Systems and methods for managing the routing and replication of data in the upload direction in a network of moving things

ABSTRACT

Communication network architectures, systems and methods for supporting a network of mobile nodes. As a non-limiting example, various aspects of this disclosure provide communication network architectures, systems, and methods for supporting a dynamically configurable communication network comprising a complex array of both static and moving communication nodes (e.g., the Internet of moving things). More specifically, systems and methods for managing the routing and replication of data in the upload direction in a network of moving things.

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This patent application makes reference to, claims priority to, andclaims benefit from U.S. Provisional Patent Application Ser. No.62/338,135, filed on May 18, 2016, and titled “Systems and Method forManaging the Routing and Replication of Data in the Upload Direction ina Network of Moving Things,” which is hereby incorporated herein byreference in its entirety. The present application is also related toU.S. Provisional Application Ser. No. 62/221,997, titled “IntegratedCommunication Network for a Network of Moving Things,” filed on Sep. 22,2015; U.S. Provisional Application Ser. No. 62/222,016, titled “Systemsand Methods for Synchronizing a Network of Moving Things,” filed on Sep.22, 2015; U.S. Provisional Application Ser. No. 62/222,042, titled“Systems and Methods for Managing a Network of Moving Things,” filed onSep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,066, titled“Systems and Methods for Monitoring a Network of Moving Things,” filedon Sep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,077,titled “Systems and Methods for Detecting and Classifying Anomalies in aNetwork of Moving Things,” filed on Sep. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/222,098, titled “Systems and Methods forManaging Mobility in a Network of Moving Things,” filed on Sep. 22,2015; U.S. Provisional Application Ser. No. 62/222,121, titled “Systemsand Methods for Managing Connectivity a Network of Moving Things,” filedon Sep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,135,titled “Systems and Methods for Collecting Sensor Data in a Network ofMoving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,145, titled “Systems and Methods for Interfacing with aNetwork of Moving Things,” filed on Sep. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/222,150, titled “Systems and Methods forInterfacing with a User of a Network of Moving Things,” filed on Sep.22, 2015; U.S. Provisional Application Ser. No. 62/222,168, titled“Systems and Methods for Data Storage and Processing for a Network ofMoving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,183, titled “Systems and Methods for Vehicle TrafficManagement in a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,186, titled “Systems and Methodsfor Environmental Management in a Network of Moving Things,” filed onSep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,190, titled“Systems and Methods for Port Management in a Network of Moving Things,”filed on Sep. 22, 2015; U.S. Provisional Patent Application Ser. No.62/222,192, titled “Communication Network of Moving Things,” filed onSep. 22, 2015; U.S. Provisional Application Ser. No. 62/244,828, titled“Utilizing Historical Data to Correct GPS Data in a Network of MovingThings,” filed on Oct. 22, 2015; U.S. Provisional Application Ser. No.62/244,930, titled “Using Anchors to Correct GPS Data in a Network ofMoving Things,” filed on Oct. 22, 2015; U.S. Provisional ApplicationSer. No. 62/246,368, titled “Systems and Methods for Inter-ApplicationCommunication in a Network of Moving Things,” filed on Oct. 26, 2015;U.S. Provisional Application Ser. No. 62/246,372, titled “Systems andMethods for Probing and Validating Communication in a Network of MovingThings,” filed on Oct. 26, 2015; U.S. Provisional Application Ser. No.62/250,544, titled “Adaptive Rate Control for Vehicular Networks,” filedon Nov. 4, 2015; U.S. Provisional Application Ser. No. 62/273,878 titled“Systems and Methods for Reconfiguring and Adapting Hardware in aNetwork of Moving Things,” filed on Dec. 31, 2015; U.S. ProvisionalApplication Ser. No. 62/253,249, titled “Systems and Methods forOptimizing Data Gathering in a Network of Moving Things,” filed on Nov.10, 2015; U.S. Provisional Application Ser. No. 62/257,421, titled“Systems and Methods for Delay Tolerant Networking in a Network ofMoving Things,” filed on Nov. 19, 2015; U.S. Provisional ApplicationSer. No. 62/265,267, titled “Systems and Methods for Improving Coverageand Throughput of Mobile Access Points in a Network of Moving Things,”filed on Dec. 9, 2015; U.S. Provisional Application Ser. No. 62/270,858,titled “Channel Coordination in a Network of Moving Things,” filed onDec. 22, 2015; U.S. Provisional Application Ser. No. 62/257,854, titled“Systems and Methods for Network Coded Mesh Networking in a Network ofMoving Things,” filed on Nov. 20, 2015; U.S. Provisional ApplicationSer. No. 62/260,749, titled “Systems and Methods for Improving FixedAccess Point Coverage in a Network of Moving Things,” filed on Nov. 30,2015; U.S. Provisional Application Ser. No. 62/273,715, titled “Systemsand Methods for Managing Mobility Controllers and Their NetworkInteractions in a Network of Moving Things,” filed on Dec. 31, 2015;U.S. Provisional Application Ser. No. 62/281,432, titled “Systems andMethods for Managing and Triggering Handovers of Mobile Access Points ina Network of Moving Things,” filed on Jan. 21, 2016; U.S. ProvisionalApplication Ser. No. 62/268,188, titled “Captive Portal-related Controland Management in a Network of Moving Things,” filed on Dec. 16, 2015;U.S. Provisional Application Ser. No. 62/270,678, titled “Systems andMethods to Extrapolate High-Value Data from a Network of Moving Things,”filed on Dec. 22, 2015; U.S. Provisional Application Ser. No.62/272,750, titled “Systems and Methods for Remote Software Update andDistribution in a Network of Moving Things,” filed on Dec. 30, 2015;U.S. Provisional Application Ser. No. 62/278,662, titled “Systems andMethods for Remote Configuration Update and Distribution in a Network ofMoving Things,” filed on Jan. 14, 2016; U.S. Provisional ApplicationSer. No. 62/286,243, titled “Systems and Methods for Adapting a Networkof Moving Things Based on User Feedback,” filed on Jan. 22, 2016; U.S.Provisional Application Ser. No. 62/278,764, titled “Systems and Methodsto Guarantee Data Integrity When Building Data Analytics in a Network ofMoving Things,” Jan. 14, 2016; U.S. Provisional Application Ser. No.62/286,515, titled “Systems and Methods for Self-Initialization andAutomated Bootstrapping of Mobile Access Points in a Network of MovingThings,” filed on Jan. 25, 2016; U.S. Provisional Application Ser. No.62/295,602, titled “Systems and Methods for Power Management in aNetwork of Moving Things,” filed on Feb. 16, 2016; U.S. ProvisionalApplication Ser. No. 62/257,421, titled “Systems and Methods for DelayTolerant Networking in a Network of Moving Things,” filed Nov. 19, 2015;and U.S. Provisional Application Ser. No. 62/299,269, titled “Systemsand Methods for Automating and Easing the Installation and Setup of theInfrastructure Supporting a Network of Moving Things,” filed on Feb. 24,2016; each of which is hereby incorporated herein by reference in itsentirety for all purposes.

BACKGROUND

Current communication networks are unable to adequately supportcommunication environments involving mobile and static nodes. As anon-limiting example, current communication networks are unable toadequately support a network comprising a complex array of both movingand static nodes (e.g., the Internet of moving things, autonomousvehicle networks, etc.). Limitations and disadvantages of conventionalmethods and systems will become apparent to one of skill in the art,through comparison of such approaches with some aspects of the presentmethods and systems set forth in the remainder of this disclosure withreference to the drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 2 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 3 shows a diagram of a metropolitan area network, in accordancewith various aspects of this disclosure.

FIG. 4 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIGS. 5A-5C show a plurality of network configurations illustrating theflexibility and/or and resiliency of a communication network, inaccordance with various aspects of this disclosure.

FIG. 6 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 7 shows a block diagram of an example mobile AP in a network ofmoving things, in accordance with various aspects of the presentdisclosure.

FIG. 8 shows a block diagram of example delay tolerant networkingfunctionality for implementing data retention and dissemination rules ofnodes of a network of moving things, in accordance with various aspectsof the present disclosure.

FIG. 9 is a flowchart illustrating an example process for managing datastorage/retention and dissemination of a bundle in the upstreamdirection, in accordance with various aspects of the present disclosure.

FIGS. 10A and 10B show a flowchart illustrating an example method ofrouting and replication of data, in accordance with various aspects ofthe present disclosure.

FIGS. 11A through 11C are a flowchart illustrating an example method ofoperating a node, in accordance with various aspects of the presentdisclosure.

SUMMARY

Various aspects of this disclosure provide communication networkarchitectures, systems and methods for supporting a network of mobileand/or static nodes. As a non-limiting example, various aspects of thisdisclosure provide communication network architectures, systems, andmethods for supporting a dynamically configurable communication networkcomprising a complex array of both static and moving communication nodes(e.g., the Internet of moving things, autonomous vehicle networks,etc.). For example, a communication network implemented in accordancewith various aspects of the present disclosure may operate in one of aplurality of modalities comprising various fixed nodes, mobile nodes,and/or a combination thereof, which are selectable to achieve any of avariety of system goals.

DETAILED DESCRIPTION OF VARIOUS ASPECTS OF THE DISCLOSURE

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e., hardware) and any software and/orfirmware (“code”) that may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory (e.g., a volatileor non-volatile memory device, a general computer-readable medium, etc.)may comprise a first “circuit” when executing a first one or more linesof code and may comprise a second “circuit” when executing a second oneor more lines of code. Additionally, a circuit may comprise analogand/or digital circuitry. Such circuitry may, for example, operate onanalog and/or digital signals. It should be understood that a circuitmay be in a single device or chip, on a single motherboard, in a singlechassis, in a plurality of enclosures at a single geographical location,in a plurality of enclosures distributed over a plurality ofgeographical locations, etc. Similarly, the term “module” may, forexample, refer to a physical electronic components (i.e., hardware) andany software and/or firmware (“code”) that may configure the hardware,be executed by the hardware, and or otherwise be associated with thehardware.

As utilized herein, circuitry is “operable” to perform a functionwhenever the circuitry comprises the necessary hardware and code (if anyis necessary) to perform the function, regardless of whether performanceof the function is disabled, or not enabled (e.g., by auser-configurable setting, factory setting or trim, etc.).

As utilized herein, “and/or” means any one or more of the items in thelist joined by “and/or”. As an example, “x and/or y” means any elementof the three-element set {(x), (y), (x, y)}. That is, “x and/or y” means“one or both of x and y.” As another example, “x, y, and/or z” means anyelement of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z),(x, y, z)}. That is, “x, y, and/or z” means “one or more of x, y, andz.” As utilized herein, the terms “e.g.,” and “for example,”“exemplary,” and the like set off lists of one or more non-limitingexamples, instances, or illustrations.

The terminology used herein is for the purpose of describing particularexamples only and is not intended to be limiting of the disclosure. Asused herein, the singular forms are intended to include the plural formsas well, unless the context clearly indicates otherwise. It will befurther understood that the terms “comprises,” “includes,” “comprising,”“including,” “has,” “have,” “having,” and the like when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another element. Thus, for example, a first element, afirst component or a first section discussed below could be termed asecond element, a second component or a second section without departingfrom the teachings of the present disclosure. Similarly, various spatialterms, such as “upper,” “lower,” “side,” and the like, may be used indistinguishing one element from another element in a relative manner. Itshould be understood, however, that components may be oriented indifferent manners, for example an electronic device may be turnedsideways so that its “top” surface is facing horizontally and its “side”surface is facing vertically, without departing from the teachings ofthe present disclosure.

With the proliferation of the mobile and/or static things (e.g.,devices, machines, people, etc.) and logistics for such things to becomeconnected to each other (e.g., in the contexts of smart logistics,transportation, environmental sensing, etc.), a platform that is forexample always-on, robust, scalable and secure that is capable ofproviding connectivity, services and Internet access to such things (orobjects), anywhere and anytime is desirable. Efficient power utilizationwithin the various components of such system is also desirable.

Accordingly, various aspects of the present disclosure provide afully-operable, always-on, responsive, robust, scalable, secureplatform/system/architecture to provide connectivity, services andInternet access to all mobile things and/or static things (e.g.,devices, machines, people, access points, end user devices, sensors,etc.) anywhere and anytime, while operating in an energy-efficientmanner.

Various aspects of the present disclosure provide a platform that isflexibly configurable and adaptable to the various requirements,features, and needs of different environments, where each environmentmay be characterized by a respective level of mobility and density ofmobile and/or static things, and the number and/or types of access tothose things. Characteristics of various environments may, for example,include high mobility of nodes (e.g., causing contacts or connections tobe volatile), high number of neighbors, high number of connected mobileusers, mobile access points, availability of multiple networks andtechnologies (e.g., sometimes within a same area), etc. For example, themode of operation of the platform may be flexibly adapted fromenvironment to environment, based on each environment's respectiverequirements and needs, which may be different from other environments.Additionally for example, the platform may be flexibly optimized (e.g.,at design/installation time and/or in real-time) for different purposes(e.g., to reduce the latency, increase throughput, reduce powerconsumption, load balance, increase reliability, make more robust withregard to failures or other disturbances, etc.), for example based onthe content, service or data that the platform provides or handleswithin a particular environment.

In accordance with various aspects of the present disclosure, manycontrol and management services (e.g., mobility, security, routing,etc.) are provided on top of the platform (e.g., directly, using controloverlays, using containers, etc.), such services being compatible withthe services currently deployed on top of the Internet or othercommunication network(s).

The communication network (or platform), in whole or in part, may forexample be operated in public and/or private modes of operation, forexample depending on the use case. The platform may, for example,operate in a public or private mode of operation, depending on theuse-case (e.g., public Internet access, municipal environment sensing,fleet operation, etc.).

Additionally for example, in an implementation in which various networkcomponents are mobile, the transportation and/or signal controlmechanisms may be adapted to serve the needs of the particularimplementation. Also for example, wireless transmission power and/orrate may be adapted (e.g., to mitigate interference, to reduce powerconsumption, to extend the life of network components, etc.

Various example implementations of a platform, in accordance withvarious aspects of the present disclosure, are capable of connectingdifferent subsystems, even when various other subsystems that maynormally be utilized are unavailable. For example, the platform maycomprise various built-in redundancies and fail-recovery mechanisms. Forexample, the platform may comprise a self-healing capability,self-configuration capability, self-adaptation capability, etc. Theprotocols and functions of the platform may, for example, be prepared tobe autonomously and smoothly configured and adapted to the requirementsand features of different environments characterized by different levelsof mobility and density of things (or objects), the number/types ofaccess to those things. For example, various aspects of the platform maygather context parameters that can influence any or all decisions. Suchparameters may, for example, be derived locally, gathered from aneighborhood, fixed APs, the Cloud, etc. Various aspects of the platformmay also, for example, ask for historical information to feed any of thedecisions, where such information can be derived from historical data,from surveys, from simulators, etc. Various aspects of the platform mayadditionally, for example, probe or monitor decisions made throughoutthe network, for example to evaluate the network and/or the decisionsthemselves in real-time. Various aspects of the platform may further,for example, enforce the decisions in the network (e.g., afterevaluating the probing results). Various aspects of the platform may,for example, establish thresholds to avoid any decision that is to beconstantly or repeatedly performed without any significant advantage(e.g., technology change, certificate change, IP change, etc.). Variousaspects of the platform may also, for example, learn locally (e.g., withthe decisions performed) and dynamically update the decisions.

In addition to (or instead of) failure robustness, a platform mayutilize multiple connections (or pathways) that exist between distinctsub-systems or elements within the same sub-system, to increase therobustness and/or load-balancing of the system.

The following discussion will present examples of the functionalityperformed by various example subsystems of the communication network. Itshould be understood that the example functionality discussed hereinneed not be performed by the particular example subsystem or by a singlesubsystem. For example, the subsystems present herein may interact witheach other, and data or control services may be deployed either in acentralized way, or having their functionalities distributed among thedifferent subsystems, for example leveraging the cooperation between theelements of each subsystem.

Various aspects of the present disclosure provide a communicationnetwork (e.g., a city-wide vehicular network, a shipping port-sizedvehicular network, a campus-wide vehicular network, etc.) that utilizesvehicles (e.g., automobiles, buses, trucks, boats, forklifts,human-operated vehicles, autonomous and/or remote controlled vehicles,etc.) as Wi-Fi hotspots. Note that Wi-Fi is generally used throughoutthis discussion as an example, but the scope of various aspects of thisdisclosure is not limited thereto. For example, other wireless LANtechnologies, PAN technologies, MAN technologies, etc., may be utilized.Such utilization may, for example, provide cost-effective ways to gathersubstantial amounts of urban data, and provide for the efficientoffloading of traffic from congested cellular networks (or othernetworks). In controlled areas (e.g., ports, harbors, etc.) with manyvehicles, a communication network in accordance with various aspects ofthis disclosure may expand the wireless coverage of existing enterpriseWi-Fi networks, for example providing for real-time communication withvehicle drivers (e.g., human, computer-controlled, etc.) and othermobile employees without the need for SIM cards or cellular (or othernetwork) data plans.

Vehicles may have many advantageous characteristics that make themuseful as Wi-Fi (or general wireless) hotspots. For example, vehiclesgenerally have at least one battery, vehicles are generally denselyspread over the city at street level and/or they are able to establishmany contacts with each other in a controlled space, and vehicles cancommunicate with 10× the range of normal Wi-Fi in the 5.9 GHz frequencyband, reserved for intelligent transportation systems in the EU, theU.S., and elsewhere. Note that the scope of this disclosure is notlimited to such 5.9 GHz wireless communication. Further, vehicles areable to effectively expand their coverage area into a swath over aperiod of time, enabling a single vehicle access point to interact withsubstantially more data sources over the period of time.

In accordance with various aspects of the present disclosure, anaffordable multi-network on-board unit (OBU) is presented. Note that theOBU may also be referred to herein as a mobile access point, Mobile AP,MAP, etc. The OBU may, for example, comprise a plurality of networkinginterfaces (e.g., Wi-Fi, 802.11p, 4G, Bluetooth, UWB, etc.). The OBUmay, for example, be readily installed in or on private and/or publicvehicles (e.g., individual user vehicles, vehicles of private fleets,vehicles of public fleets, etc.). The OBU may, for example, be installedin transportation fleets, waste management fleets, law enforcementfleets, emergency services, road maintenance fleets, taxi fleets,aircraft fleets, etc. The OBU may, for example, be installed in or on avehicle or other structure with free mobility or relatively limitedmobility. The OBU may also, for example, be carried by a person orservice animal, mounted to a bicycle, mounted to a moving machine ingeneral, mounted to a container, etc.

The OBUs may, for example, operate to connect passing vehicles to thewired infrastructure of one or more network providers, telecomoperators, etc. In accordance with the architecture, hardware, andsoftware functionality discussed herein, vehicles and fleets can beconnected not just to the cellular networks (or other wide area ormetropolitan area networks, etc.) and existing Wi-Fi hotspots spreadover a city or a controlled space, but also to other vehicles (e.g.,utilizing multi-hop communications to a wired infrastructure, single ormulti-hop peer-to-peer vehicle communication, etc.). The vehicles and/orfleets may, for example, form an overall mesh of communication links,for example including the OBUs and also fixed Access Points (APs)connected to the wired infrastructure (e.g., a local infrastructure,etc.). Note that OBUs herein may also be referred to as “Mobile APs,”“mobile hotspots,” “MAPs,” etc. Also note that fixed access points mayalso be referred to herein as Road Side Units (RSUs), Fixed APs, FAPs,etc.

In an example implementation, the OBUs may communicate with the FixedAPs utilizing a relatively long-range protocol (e.g., 802.11p, etc.),and the Fixed APs may, in turn, be hard wired to the wiredinfrastructure (e.g., via cable, tethered optical link, etc.). Note thatFixed APs may also, or alternatively, be coupled to the infrastructurevia wireless link (e.g., 802.11p, etc.). Additionally, clients or userdevices may communicate with the OBUs using one or more relativelyshort-range protocols (e.g., Wi-Fi, Bluetooth, UWB, etc.). The OBUs, forexample having a longer effective wireless communication range thantypical Wi-Fi access points or other wireless LAN/PAN access points(e.g., at least for links such as those based on 802.11p, etc.), arecapable of substantially greater coverage areas than typical Wi-Fi orother wireless LAN/PAN access points, and thus fewer OBUs are necessaryto provide blanket coverage over a geographical area.

The OBU may, for example, comprise a robust vehicular networking module(e.g., a connection manager) which builds on long-range communicationprotocol capability (e.g., 802.11p, etc.). For example, in addition tocomprising 802.11p (or other long-range protocol) capability tocommunicate with Fixed APs, vehicles, and other nodes in the network,the OBU may comprise a network interface (e.g., 802.11a/b/g/n, 802.11ac,802.11af, any combination thereof, etc.) to provide wireless local areanetwork (WLAN) connectivity to end user devices, sensors, fixed Wi-Fiaccess points, etc. For example, the OBU may operate to providein-vehicle Wi-Fi Internet access to users in and/or around the vehicle(e.g., a bus, train car, taxi cab, public works vehicle, etc.). The OBUmay further comprise one or more wireless backbone communicationinterfaces (e.g., cellular network interfaces, etc.). Though in variousexample scenarios, a cellular network interface (or other wirelessbackbone communication interface) might not be the preferred interfacefor various reasons (e.g., cost, power, bandwidth, etc.), the cellularnetwork interface may be utilized to provide connectivity ingeographical areas that are not presently supported by a Fixed AP, maybe utilized to provide a fail-over communication link, may be utilizedfor emergency communications, may be utilized to subscribe to localinfrastructure access, etc. The cellular network interface may also, forexample, be utilized to allow the deployment of solutions that aredependent on the cellular network operators.

An OBU, in accordance with various aspects of the present disclosure,may for example comprise a smart connection manager that can select thebest available wireless link(s) (e.g., Wi-Fi, 802.11p, cellular, vehiclemesh, etc.) with which to access the Internet. The OBU may also, forexample, provide geo-location capabilities (e.g., GPS, etc.), motiondetection sensors to determine if the vehicle is in motion, and a powercontrol subsystem (e.g., to ensure that the OBU does not deplete thevehicle battery, etc.). The OBU may, for example, comprise any or all ofthe sensors (e.g., environmental sensors, etc.) discussed herein.

The OBU may also, for example, comprise a manager that managesmachine-to-machine data acquisition and transfer (e.g., in a real-timeor delay-tolerant fashion) to and from the cloud. For example, the OBUmay log and/or communicate information of the vehicles.

The OBU may, for example, comprise a connection and/or routing managerthat operates to perform routing of communications in avehicle-to-vehicle/vehicle-to-infrastructure multi-hop communication. Amobility manager (or controller, MC) may, for example, ensure thatcommunication sessions persist over one or more handoff(s) (alsoreferred to herein as a “handover” or “handovers”) (e.g., betweendifferent Mobile APs, Fixed APs, base stations, hot spots, etc.), amongdifferent technologies (e.g., 802.11p, cellular, Wi-Fi, satellite,etc.), among different MCs (e.g., in a fail-over scenario, loadredistribution scenario, etc.), across different interfaces (or ports),etc. Note that the MC may also be referred to herein as a Local MobilityAnchor (LMA), a Network Controller, etc. Note that the MC, or aplurality thereof, may for example be implemented as part of thebackbone, but may also, or alternatively, be implemented as part of anyof a variety of components or combinations thereof. For example, the MCmay be implemented in a Fixed AP (or distributed system thereof), aspart of an OBU (or a distributed system thereof), etc. Variousnon-limiting examples of system components and/or methods are providedin U.S. Provisional Application No. 62/222,098, filed Sep. 22, 2015, andtitled “Systems and Method for Managing Mobility in a Network of MovingThings,” the entire contents of which are hereby incorporated herein byreference. Note that in an example implementation including a pluralityof MCs, such MCs may be co-located and/or may be geographicallydistributed.

Various aspects of the present disclosure also provide a cloud-basedservice-oriented architecture that handles the real-time management,monitoring and reporting of the network and clients, the functionalitiesrequired for data storage, processing and management, the Wi-Fi clientauthentication and Captive Portal display, etc.

A communication network (or component thereof) in accordance withvarious aspects of the present disclosure may, for example, support awide range of smart city applications (or controlled scenarios, orconnected scenarios, etc.) and/or use-cases, as described herein.

For example, an example implementation may operate to turn each vehicle(e.g., both public and private taxis, buses, trucks, etc.) into a MobileAP (e.g., a mobile Wi-Fi hotspot), offering Internet access toemployees, passengers and mobile users travelling in the city, waitingin bus stops, sitting in parks, etc. Moreover, through an examplevehicular mesh network formed between vehicles and/or fleets ofvehicles, an implementation may be operable to offload cellular trafficthrough the mobile Wi-Fi hotspots and/or fixed APs (e.g., 802.11p-basedAPs) spread over the city and connected to the wired infrastructure ofpublic or private telecom operators in strategic places, while ensuringthe widest possible coverage at the lowest possible cost.

An example implementation (e.g., of a communication network and/orcomponents thereof) may, for example, be operable as a massive urbanscanner that gathers large amounts of data (e.g., continuously)on-the-move, actionable or not, generated by a myriad of sourcesspanning from the in-vehicle sensors or On Board Diagnostic System port(e.g., OBD2, etc.), interface with an autonomous vehicle driving system,external Wi-Fi/Bluetooth-enabled sensing units spread over the city,devices of vehicles' drivers and passengers (e.g., informationcharacterizing such devices and/or passengers, etc.), positioning systemdevices (e.g., position information, velocity information, trajectoryinformation, travel history information, etc.), etc.

Depending on the use case, the OBU may for example process (or computer,transform, manipulate, aggregate, summarize, etc.) the data beforesending the data from the vehicle, for example providing the appropriategranularity (e.g., value resolution) and sampling rates (e.g., temporalresolution) for each individual application. For example, the OBU may,for example, process the data in any manner deemed advantageous by thesystem. The OBU may, for example, send the collected data (e.g., rawdata, preprocessed data, information of metrics calculated based on thecollected data, etc.) to the Cloud (e.g., to one or more networkedservers coupled to any portion of the network) in an efficient andreliable manner to improve the efficiency, environmental impact andsocial value of municipal city operations and transportation services.Various example use cases are described herein.

In an example scenario in which public buses are moving along cityroutes and/or taxis are performing their private transportationservices, the OBU is able to collect large quantities of real-time datafrom the positioning systems (e.g., GPS, etc.), from accelerometermodules, etc. The OBU may then, for example, communicate such data tothe Cloud, where the data may be processed, reported and viewed, forexample to support such public or private bus and/or taxi operations,for example supporting efficient remote monitoring and scheduling ofbuses and taxis, respectively.

In an example implementation, small cameras (or other sensors) may becoupled to small single-board computers (SBCs) that are placed above thedoors of public buses to allow capturing image sequences of peopleentering and leaving buses, and/or on stops along the bus routes inorder to estimate the number of people waiting for a bus. Such data maybe gathered by the OBU in order to be sent to the Cloud. With such data,public transportation systems may detect peaks; overcrowded buses,routes and stops; underutilized buses, routes and stops; etc., enablingaction to be taken in real-time (e.g., reducing bus periodicity todecrease fuel costs and CO₂ emissions where and when passenger flows aresmaller, etc.) as well as detecting systematic transportation problems.

An OBU may, for example, be operable to communicate with any of avariety of Wi-Fi-enabled sensor devices equipped with a heterogeneouscollection of environmental sensors. Such sensors may, for example,comprise noise sensors (microphones, etc.), gas sensors (e.g., sensingCO, NO₂, O₃, volatile organic compounds (or VOCs), CO₂, etc.), smokesensors, pollution sensors, meteorological sensors (e.g., sensingtemperature, humidity, luminosity, particles, solar radiation, windspeed (e.g., anemometer), wind direction, rain (e.g., a pluviometer),optical scanners, biometric scanners, cameras, microphones, etc.). Suchsensors may also comprise sensors associated with users (e.g., vehicleoperators or passengers, passersby, etc.) and/or their personal devices(e.g., smart phones or watches, biometrics sensors, wearable sensors,implanted sensors, etc.). Such sensors may, for example, comprisesensors and/or systems associated with on-board diagnostic (OBD) unitsfor vehicles, autonomous vehicle driving systems, etc. Such sensors may,for example, comprise positioning sensors (e.g., GPS sensors, Galileosensors, GLONASS sensors, etc.). Note that such positioning sensors maybe part of a vehicle's operational system (e.g., a localhuman-controlled vehicle, an autonomous vehicle, a remotehuman-controlled vehicle, etc.) Such sensors may, for example, comprisecontainer sensors (e.g., garbage can sensors, shipping containersensors, container environmental sensors, container tracking sensors,etc.).

Once a vehicle enters the vicinity of such a sensor device, a wirelesslink may be established, so that the vehicle (or OBU thereof) cancollect sensor data from the sensor device and upload the collected datato a database in the Cloud. The appropriate action can then be taken. Inan example waste management implementation, several waste management (orcollection) trucks may be equipped with OBUs that are able toperiodically communicate with sensors installed on containers in orderto gather information about waste level, time passed since lastcollection, etc. Such information may then sent to the Cloud (e.g., to awaste management application coupled to the Internet, etc.) through thevehicular mesh network, in order to improve the scheduling and/orrouting of waste management trucks. Note that various sensors may alwaysbe in range of the Mobile AP (e.g., vehicle-mounted sensors). Note thatthe sensor may also (or alternatively) be mobile (e.g., a sensor mountedto another vehicle passing by a Mobile AP or Fixed AP, a drone-mountedsensor, a pedestrian-mounted sensor, etc.).

In an example implementation, for example in a controlled space (e.g., aport, harbor, airport, factory, plantation, mine, etc.) with manyvehicles, machines and employees, a communication network in accordancewith various aspects of the present disclosure may expand the wirelesscoverage of enterprise and/or local Wi-Fi networks, for example withoutresorting to a Telco-dependent solution based on SIM cards or cellularfees. In such an example scenario, apart from avoiding expensivecellular data plans, limited data rate and poor cellular coverage insome places, a communication network in accordance with various aspectsof the present disclosure is also able to collect and/or communicatelarge amounts of data, in a reliable and real-time manner, where suchdata may be used to optimize harbor logistics, transportationoperations, etc.

For example in a port and/or harbor implementation, by gatheringreal-time information on the position, speed, fuel consumption and CO₂emissions of the vehicles, the communication network allows a portoperator to improve the coordination of the ship loading processes andincrease the throughput of the harbor. Also for example, thecommunication network enables remote monitoring of drivers' behaviors,behaviors of autonomous vehicles and/or control systems thereof, trucks'positions and engines' status, and then be able to provide real-timenotifications to drivers (e.g., to turn on/off the engine, follow theright route inside the harbor, take a break, etc.), for example humandrivers and/or automated vehicle driving systems, thus reducing thenumber and duration of the harbor services and trips. Harbor authoritiesmay, for example, quickly detect malfunctioning trucks and abnormaltrucks' circulation, thus avoiding accidents in order to increase harborefficiency, security, and safety. Additionally, the vehicles can alsoconnect to Wi-Fi access points from harbor local operators, and provideWi-Fi Internet access to vehicles' occupants and surrounding harboremployees, for example allowing pilots to save time by filing reportsvia the Internet while still on the water.

FIG. 1 shows a block diagram of a communication network 100, inaccordance with various aspects of this disclosure. Any or all of thefunctionality discussed herein may be performed by any or all of theexample components of the example network 100. Also, the example network100 may, for example, share any or all characteristics with the otherexample networks and/or network components 200, 300, 400, 500-570, and600, discussed herein.

The example network 100, for example, comprises a Cloud that may, forexample comprise any of a variety of network level components. The Cloudmay, for example, comprise any of a variety of server systems executingapplications that monitor and/or control components of the network 100.Such applications may also, for example, manage the collection ofinformation from any of a large array of networked information sources,many examples of which are discussed herein. The Cloud (or a portionthereof) may also be referred to, at times, as an API. For example,Cloud (or a portion thereof) may provide one or more applicationprogramming interfaces (APIs) which other devices may use forcommunicating/interacting with the Cloud.

An example component of the Cloud may, for example, manageinteroperability with various multi-cloud systems and architectures.Another example component (e.g., a Cloud service component) may, forexample, provide various cloud services (e.g., captive portal services,authentication, authorization, and accounting (AAA) services, APIGateway services, etc.). An additional example component (e.g., aDevCenter component) may, for example, provide network monitoring and/ormanagement functionality, manage the implementation of software updates,etc. A further example component of the Cloud may manage data storage,data analytics, data access, etc. A still further example component ofthe Cloud may include any of a variety of third-partly applications andservices.

The Cloud may, for example, be coupled to the Backbone/CoreInfrastructure of the example network 100 via the Internet (e.g.,utilizing one or more Internet Service Providers). Though the Internetis provided by example, it should be understood that scope of thepresent disclosure is not limited thereto.

The Backbone/Core may, for example, comprise any one or more differentcommunication infrastructure components. For example, one or moreproviders may provide backbone networks or various components thereof.As shown in the example network 100 illustrated in FIG. 1, a Backboneprovider may provide wireline access (e.g., PSTN, fiber, cable, etc.).Also for example, a Backbone provider may provide wireless access (e.g.,Microwave, LTE/Cellular, 5G/TV Spectrum, etc.).

The Backbone/Core may also, for example, comprise one or more LocalInfrastructure Providers. The Backbone/Core may also, for example,comprise a private infrastructure (e.g., run by the network 100implementer, owner, etc.). The Backbone/Core may, for example, provideany of a variety of Backbone Services (e.g., AAA, Mobility, Monitoring,Addressing, Routing, Content services, Gateway Control services, etc.).

The Backbone/Core Infrastructure may comprise any of a variety ofcharacteristics, non-limiting examples of which are provided herein. Forexample, the Backbone/Core may be compatible with different wireless orwired technologies for backbone access. The Backbone/Core may also beadaptable to handle public (e.g., municipal, city, campus, etc.) and/orprivate (e.g., ports, campus, etc.) network infrastructures owned bydifferent local providers, and/or owned by the network implementer orstakeholder. The Backbone/Core may, for example, comprise and/orinterface with different Authentication, Authorization, and Accounting(AAA) mechanisms.

The Backbone/Core Infrastructure may, for example, support differentmodes of operation (e.g., L2 in port implementations, L3 in on-landpublic transportation implementations, utilizing any one or more of aplurality of different layers of digital IP networking, any combinationsthereof, equivalents thereof, etc.) or addressing pools. TheBackbone/Core may also for example, be agnostic to the Cloud provider(s)and/or Internet Service Provider(s). Additionally for example, theBackbone/Core may be agnostic to requests coming from any or allsubsystems of the network 100 (e.g., Mobile APs or OBUs (On BoardUnits), Fixed APs or RSUs (Road Side Units), MCs (Mobility Controllers)or LMAs (Local Mobility Anchors) or Network Controllers, etc.) and/orthird-party systems.

The Backbone/Core Infrastructure may, for example, comprise the abilityto utilize and/or interface with different data storage/processingsystems (e.g., MongoDB, MySql, Redis, etc.). The Backbone/CoreInfrastructure may further, for example, provide different levels ofsimultaneous access to the infrastructure, services, data, etc.

The example network 100 may also, for example, comprise a Fixed HotspotAccess Network. Various example characteristics of such a Fixed HotspotAccess Network 200 are shown at FIG. 2. The example network 200 may, forexample, share any or all characteristics with the other examplenetworks and/or network components 100, 300, 400, 500-570, and 600,discussed herein.

In the example network 200, the Fixed APs (e.g., the proprietary APs,the public third party APs, the private third party APs, etc.) may bedirectly connected to the local infrastructure provider and/or to thewireline/wireless backbone. Also for example, the example network 200may comprise a mesh between the various APs via wireless technologies.Note, however, that various wired technologies may also be utilizeddepending on the implementation. As shown, different fixed hotspotaccess networks can be connected to a same backbone provider, but mayalso be connected to different respective backbone providers. In anexample implementation utilizing wireless technology for backboneaccess, such an implementation may be relatively fault tolerant. Forexample, a Fixed AP may utilize wireless communications to the backbonenetwork (e.g., cellular, 3G, LTE, other wide or metropolitan areanetworks, etc.) if the backhaul infrastructure is down. Also forexample, such an implementation may provide for relatively easyinstallation (e.g., a Fixed AP with no cable power source that can beplaced virtually anywhere).

In the example network 200, the same Fixed AP can simultaneously provideaccess to multiple Fixed APs, Mobile APs (e.g., vehicle OBUs, etc.),devices, user devices, sensors, things, etc. For example, a plurality ofmobile hotspot access networks (e.g., OBU-based networks, etc.) mayutilize the same Fixed AP. Also for example, the same Fixed AP canprovide a plurality of simultaneous accesses to another single unit(e.g., another Fixed AP, Mobile AP, device, etc.), for example utilizingdifferent channels, different radios, etc.).

Note that a plurality of Fixed APs may be utilized forfault-tolerance/fail-recovery purposes. In an example implementation, aFixed AP and its fail-over AP may both be normally operational (e.g., ina same switch). Also for example, one or more Fixed APs may be placed inthe network at various locations in an inactive or monitoring mode, andready to become operational when needed (e.g., in response to a fault,in response to an emergency services need, in response to a data surge,etc.).

Referring back to FIG. 1, the example Fixed Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. Also, the example Fixed Hotspot AccessNetwork is shown with a wired communication link to one or more BackboneProviders, to the Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. The Environment may comprise any of avariety of devices (e.g., in-vehicle networks, devices, and sensors;autonomous vehicle networks, devices, and sensors; maritime (orwatercraft) and port networks, devices, and sensors; generalcontrolled-space networks, devices, and sensors; residential networks,devices, and sensors; disaster recovery & emergency networks, devices,and sensors; military and aircraft networks, devices, and sensors; smartcity networks, devices, and sensors; event (or venue) networks, devices,and sensors; underwater and underground networks, devices, and sensors;agricultural networks, devices, and sensors; tunnel (auto, subway,train, etc.) networks, devices, and sensors; parking networks, devices,and sensors; security and surveillance networks, devices, and sensors;shipping equipment and container networks, devices, and sensors;environmental control or monitoring networks, devices, and sensors;municipal networks, devices, and sensors; waste management networks,devices, and sensors, road maintenance networks, devices, and sensors,traffic management networks, devices, and sensors; advertising networks,devices and sensors; etc.).

The example network 100 of FIG. 1 also comprises a Mobile Hotspot AccessNetwork. Various example characteristics of such a Mobile Hotspot AccessNetwork 300 are shown at FIG. 3. Note that various fixed networkcomponents (e.g., Fixed APs) are also illustrated. The example network300 may, for example, share any or all characteristics with the otherexample networks and/or network components 100, 200, 400, 500-570, and600 discussed herein.

The example network 300 comprises a wide variety of Mobile APs (orhotspots) that provide access to user devices, provide for sensor datacollection, provide multi-hop connectivity to other Mobile APs, etc. Forexample, the example network 300 comprises vehicles from differentfleets (e.g., aerial, terrestrial, underground, (under)water, etc.). Forexample, the example network 300 comprises one or more massdistribution/transportation fleets, one or more mass passengertransportation fleets, private/public shared-user fleets, privatevehicles, urban and municipal fleets, maintenance fleets, drones,watercraft (e.g., boats, ships, speedboats, tugboats, barges, etc.),emergency fleets (e.g., police, ambulance, firefighter, etc.), etc.

The example network 300, for example, shows vehicles from differentfleets directly connected and/or mesh connected, for example using sameor different communication technologies. The example network 300 alsoshows fleets simultaneously connected to different Fixed APs, which mayor may not belong to different respective local infrastructureproviders. As a fault-tolerance mechanism, the example network 300 mayfor example comprise the utilization of long-range wirelesscommunication network (e.g., cellular, 3G, 4G, LTE, etc.) in vehicles ifthe local network infrastructure is down or otherwise unavailable. Asame vehicle (e.g., Mobile AP or OBU) can simultaneously provide accessto multiple vehicles, devices, things, etc., for example using a samecommunication technology (e.g., shared channels and/or differentrespective channels thereof) and/or using a different respectivecommunication technology for each. Also for example, a same vehicle canprovide multiple accesses to another vehicle, device, thing, etc., forexample using a same communication technology (e.g., shared channelsand/or different respective channels thereof, and/or using a differentcommunication technology).

Additionally, multiple network elements may be connected together toprovide for fault-tolerance or fail recovery, increased throughput, orto achieve any or a variety of a client's networking needs, many ofexamples of which are provided herein. For example, two Mobile APs (orOBUs) may be installed in a same vehicle, etc.

Referring back to FIG. 1, the example Mobile Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Fixed Hotspot Access Network, to one or more End UserDevice, and to the Environment (e.g., to any one of more of the sensorsor systems discussed herein, any other device or machine, etc.). Thoughthe Mobile Hotspot Access Network is not shown having a wired link tothe various other components, there may (at least at times) be such awired link, at least temporarily.

The example network 100 of FIG. 1 also comprises a set of End-UserDevices. Various example end user devices are shown at FIG. 4. Note thatvarious other network components (e.g., Fixed Hotspot Access Networks,Mobile Hotspot Access Network(s), the Backbone/Core, etc.) are alsoillustrated. The example network 400 may, for example, share any or allcharacteristics with the other example networks and/or networkcomponents 100, 200, 300, 500-570, and 600, discussed herein.

The example network 400 shows various mobile networked devices. Suchnetwork devices may comprise end-user devices (e.g., smartphones,tablets, smartwatches, laptop computers, webcams, personal gamingdevices, personal navigation devices, personal media devices, personalcameras, health-monitoring devices, personal location devices,monitoring panels, printers, etc.). Such networked devices may alsocomprise any of a variety of devices operating in the generalenvironment, where such devices might not for example be associated witha particular user (e.g. any or all of the sensor devices discussedherein, vehicle sensors, municipal sensors, fleet sensors road sensors,environmental sensors, security sensors, traffic sensors, waste sensors,meteorological sensors, any of a variety of different types of municipalor enterprise equipment, etc.). Any of such networked devices can beflexibly connected to distinct backbone, fixed hotspot access networks,mobile hotspot access networks, etc., using the same or differentwired/wireless technologies.

A mobile device may, for example, operate as an AP to providesimultaneous access to multiple devices/things, which may then form adhoc networks, interconnecting devices ultimately connected to distinctbackbone networks, fixed hotspot, and/or mobile hotspot access networks.Devices (e.g., any or all of the devices or network nodes discussedherein) may, for example, have redundant technologies to access distinctbackbone, fixed hotspot, and/or mobile hotspot access networks, forexample for fault-tolerance and/or load-balancing purposes (e.g.,utilizing multiple SIM cards, etc.). A device may also, for example,simultaneously access distinct backbone, fixed hotspot access networks,and/or mobile hotspot access networks, belonging to the same provider orto different respective providers. Additionally for example, a devicecan provide multiple accesses to another device/thing (e.g., viadifferent channels, radios, etc.).

Referring back to FIG. 1, the example End-User Devices are shown with awireless communication link to a backbone provider (e.g., to one or moreBackbone Providers and/or Local Infrastructure Providers), to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment. Also for example, the example End-User Devices are shownwith a wired communication link to a backbone provider, to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment.

The example network 100 illustrated in FIG. 1 has a flexiblearchitecture that is adaptable at implementation time (e.g., fordifferent use cases) and/or adaptable in real-time, for example asnetwork components enter and leave service. FIGS. 5A-5C illustrate suchflexibility by providing example modes (or configurations). The examplenetworks 500-570 may, for example, share any or all characteristics withthe other example networks and/or network components 100, 200, 300, 400,and 600, discussed herein. For example and without limitation, any orall of the communication links (e.g., wired links, wireless links, etc.)shown in the example networks 500-570 are generally analogous tosimilarly positioned communication links shown in the example network100 of FIG. 1.

For example, various aspects of this disclosure provide communicationnetwork architectures, systems, and methods for supporting a dynamicallyconfigurable communication network comprising a complex array of bothstatic and moving communication nodes (e.g., the Internet of movingthings). For example, a communication network implemented in accordancewith various aspects of the present disclosure may operate in one of aplurality of modalities comprising various fixed nodes, mobile nodes,and/or a combination thereof, which are selectable to yield any of avariety of system goals (e.g., increased throughput, reduced latency andpacket loss, increased availability and robustness of the system, extraredundancy, increased responsiveness, increased security in thetransmission of data and/or control packets, reduced number ofconfiguration changes by incorporating smart thresholds (e.g., change oftechnology, change of certificate, change of IP, etc.), providingconnectivity in dead zones or zones with difficult access, reducing thecosts for maintenance and accessing the equipment forupdating/upgrading, etc.). At least some of such modalities may, forexample, be entirely comprised of fixed-position nodes, at leasttemporarily if not permanently.

For illustrative simplicity, many of the example aspects shown in theexample system or network 100 of FIG. 1 (and other Figures herein) areomitted from FIGS. 5A-5C, but may be present. For example, the Cloud,Internet, and ISP aspects shown in FIG. 1 and in other Figures are notexplicitly shown in FIGS. 5A-5C, but may be present in any of theexample configurations (e.g., as part of the backbone provider networkor coupled thereto, as part of the local infrastructure provider networkor coupled thereto, etc.).

For example, the first example mode 500 is presented as a normalexecution mode, for example a mode (or configuration) in which all ofthe components discussed herein are present. For example, thecommunication system in the first example mode 500 comprises a backboneprovider network, a local infrastructure provider network, a fixedhotspot access network, a mobile hotspot access network, end-userdevices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via a wired link. Note that such a wiredcoupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the first example mode 500 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Also note that in various example configurations,the backbone provider network may also be communicatively coupled to thelocal infrastructure provider network via one or more wireless (ornon-tethered) links.

Though not shown in the first example mode 500 (or any of the examplemodes of FIGS. 5A-5C), one or more servers may be communicativelycoupled to the backbone provider network and/or the local infrastructurenetwork. FIG. 1 provides an example of cloud servers beingcommunicatively coupled to the backbone provider network via theInternet.

As additionally shown in FIG. 5A, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the first example mode 500(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the fixed hotspot access network (or any componentthereof), the mobile hotspot access network (or any component thereof),the end-user devices, and/or environment devices via one or morewireless links. Note that the communication link shown in the firstexample mode 500 of FIG. 5A between the local infrastructure providernetwork and the fixed hotspot access network may be wired and/orwireless.

The fixed hotspot access network is also shown in the first example mode500 to be communicatively coupled to the mobile hotspot access network,the end-user devices, and/or environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Additionally, the mobile hotspot access network is further shownin the first example mode 500 to be communicatively coupled to theend-user devices and/or environment devices via one or more wirelesslinks. Many examples of such wireless coupling are provided herein.Further, the end-user devices are also shown in the first example mode500 to be communicatively coupled to the environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Note that in various example implementations any ofsuch wireless links may instead (or in addition) comprise a wired (ortethered) link.

In the first example mode 500 (e.g., the normal mode), information (ordata) may be communicated between an end-user device and a server (e.g.,a computer system) via the mobile hotspot access network, the fixedhotspot access network, the local infrastructure provider network,and/or the backbone provider network. As will be seen in the variousexample modes presented herein, such communication may flexibly occurbetween an end-user device and a server via any of a variety ofdifferent communication pathways, for example depending on theavailability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an end user device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network).

Similarly, in the first example mode 500 (e.g., the normal mode),information (or data) may be communicated between an environment deviceand a server via the mobile hotspot access network, the fixed hotspotaccess network, the local infrastructure provider network, and/or thebackbone provider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network and/or backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an environment device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or fixed hotspotaccess network).

As discussed herein, the example networks presented herein areadaptively configurable to operate in any of a variety of differentmodes (or configurations). Such adaptive configuration may occur atinitial installation and/or during subsequent controlled networkevolution (e.g., adding or removing any or all of the network componentsdiscussed herein, expanding or removing network capacity, adding orremoving coverage areas, adding or removing services, etc.). Suchadaptive configuration may also occur in real-time, for example inresponse to real-time changes in network conditions (e.g., networks orcomponents thereof being available or not based on vehicle oruser-device movement, network or component failure, network or componentreplacement or augmentation activity, network overloading, etc.). Thefollowing example modes are presented to illustrate characteristics ofvarious modes in which a communication system may operate in accordancewith various aspects of the present disclosure. The following examplemodes will generally be discussed in relation to the first example mode500 (e.g., the normal execution mode). Note that such example modes aremerely illustrative and not limiting.

The second example mode (or configuration) 510 (e.g., a no backboneavailable mode) may, for example, share any or all characteristics withthe first example mode 500, albeit without the backbone provider networkand communication links therewith. For example, the communication systemin the second example mode 510 comprises a local infrastructure providernetwork, a fixed hotspot access network, a mobile hotspot accessnetwork, end-user devices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the second example mode 510 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary. Also note thatin various example configurations, the local infrastructure providernetwork may also, at least temporarily, be communicatively coupled tothe mobile hotspot access network (or any component thereof) via one ormore wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the second example mode 510 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Note that the communication link(s) shown in thesecond example mode 510 of FIG. 5A between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the second examplemode 510 to be communicatively coupled to the mobile hotspot accessnetwork, the end-user devices, and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Additionally, the mobile hotspot access network isfurther shown in the second example mode 510 to be communicativelycoupled to the end-user devices and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Further, the end-user devices are also shown in thesecond example mode 510 to be communicatively coupled to the environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Note that in various exampleimplementations any of such wireless links may instead (or in addition)comprise a wired (or tethered) link.

In the second example mode 510 (e.g., the no backbone available mode),information (or data) may be communicated between an end-user device anda server (e.g., a computer, etc.) via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. As will be seen in the various example modes presentedherein, such communication may flexibly occur between an end-user deviceand a server via any of a variety of different communication pathways,for example depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the fixed hotspot access network and/or the local infrastructureprovider network (e.g., skipping the mobile hotspot access network).Also for example, information communicated between an end user deviceand a server may be communicated via the local infrastructure providernetwork (e.g., skipping the mobile hotspot access network and/or fixedhotspot access network).

Similarly, in the second example mode 510 (e.g., the no backboneavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network) via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network and/orthe local infrastructure provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thelocal infrastructure provider network (e.g., skipping the mobile hotspotaccess network and/or fixed hotspot access network).

The second example mode 510 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. Forexample, due to security and/or privacy goals, the second example mode510 may be utilized so that communication access to the public Cloudsystems, the Internet in general, etc., is not allowed. For example, allnetwork control and management functions may be within the localinfrastructure provider network (e.g., wired local network, etc.) and/orthe fixed access point network.

In an example implementation, the communication system might be totallyowned, operated and/or controlled by a local port authority. No extraexpenses associated with cellular connections need be spent. Forexample, cellular connection capability (e.g., in Mobile APs, Fixed APs,end user devices, environment devices, etc.) need not be provided. Notealso that the second example mode 510 may be utilized in a scenario inwhich the backbone provider network is normally available but iscurrently unavailable (e.g., due to server failure, due to communicationlink failure, due to power outage, due to a temporary denial of service,etc.).

The third example mode (or configuration) 520 (e.g., a no localinfrastructure and fixed hotspots available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, the fixed hotspotaccess network, and communication links therewith. For example, thecommunication system in the third example mode 520 comprises a backboneprovider network, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the third example mode 520 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the third example mode 520 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links.

The mobile hotspot access network is further shown in the third examplemode 520 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the third example mode 520 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Note that in various example implementations any of suchwireless links may instead (or in addition) comprise a wired (ortethered) link.

In the third example mode 520 (e.g., the no local infrastructure andfixed hotspots available mode), information (or data) may becommunicated between an end-user device and a server (e.g., a computer,etc.) via the mobile hotspot access network and/or the backbone providernetwork. As will be seen in the various example modes presented herein,such communication may flexibly occur between an end-user device and aserver via any of a variety of different communication pathways, forexample depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the backbone provider network (e.g., skipping the mobile hotspotaccess network).

Similarly, in the third example mode 520 (e.g., the no localinfrastructure and fixed hotspots available mode), information (or data)may be communicated between an environment device and a server via themobile hotspot access network and/or the backbone provider network. Alsofor example, an environment device may communicate with or through anend-user device (e.g., instead of or in addition to the mobile hotspotaccess network). As will be seen in the various example modes presentedherein, such communication may flexibly occur between an environmentdevice and a server (e.g., communicatively coupled to the backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the backbone provider network (e.g., skipping themobile hotspot access network).

In the third example mode 520, all control/management functions may forexample be implemented within the Cloud. For example, since the mobilehotspot access network does not have a communication link via a fixedhotspot access network, the Mobile APs may utilize a direct connection(e.g., a cellular connection) with the backbone provider network (orCloud). If a Mobile AP does not have such capability, the Mobile AP mayalso, for example, utilize data access provided by the end-user devicescommunicatively coupled thereto (e.g., leveraging the data plans of theend-user devices).

The third example mode 520 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the third example mode 520 may be utilized in anearly stage of a larger deployment, for example deployment that willgrow into another mode (e.g., the example first mode 500, example fourthmode 530, etc.) as more communication system equipment is installed.Note also that the third example mode 520 may be utilized in a scenarioin which the local infrastructure provider network and fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The fourth example mode (or configuration) 530 (e.g., a no fixedhotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thefixed hotspot access network and communication links therewith. Forexample, the communication system in the fourth example mode 530comprises a backbone provider network, a local infrastructure providernetwork, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), the end-userdevices, and/or environment devices via one or more wired links. Notethat such a wired coupling may be temporary. Also note that in variousexample configurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fourth example mode 530 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fourth example mode 530(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wired links. Note that such a wired coupling may betemporary. Also note that in various example configurations, the localinfrastructure provider network may also, at least temporarily, becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof) via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links.

The mobile hotspot access network is further shown in the fourth examplemode 530 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fourth example mode 530 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fourth example mode 530 (e.g., the no fixed hotspots mode),information (or data) may be communicated between an end-user device anda server via the mobile hotspot access network, the local infrastructureprovider network, and/or the backbone provider network. As will be seenin the various example modes presented herein, such communication mayflexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider networkand/or the backbone provider network (e.g., skipping the mobile hotspotaccess network). Also for example, information communicated between anend user device and a server may be communicated via the backboneprovider network (e.g., skipping the mobile hotspot access networkand/or local infrastructure provider network).

Similarly, in the fourth example mode 530 (e.g., the no fixed hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to themobile hotspot access network). As will be seen in the various examplemodes presented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the mobile hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or backboneprovider network).

In the fourth example mode 530, in an example implementation, some ofthe control/management functions may for example be implemented withinthe local backbone provider network (e.g., within a client premises).For example, communication to the local infrastructure provider may beperformed through the backbone provider network (or Cloud). Note that ina scenario in which there is a direct communication pathway between thelocal infrastructure provider network and the mobile hotspot accessnetwork, such communication pathway may be utilized.

For example, since the mobile hotspot access network does not have acommunication link via a fixed hotspot access network, the Mobile APsmay utilize a direct connection (e.g., a cellular connection) with thebackbone provider network (or Cloud). If a Mobile AP does not have suchcapability, the Mobile AP may also, for example, utilize data accessprovided by the end-user devices communicatively coupled thereto (e.g.,leveraging the data plans of the end-user devices).

The fourth example mode 530 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the fourth example mode 530 may be utilized inan early stage of a larger deployment, for example a deployment thatwill grow into another mode (e.g., the example first mode 500, etc.) asmore communication system equipment is installed. The fourth examplemode 530 may, for example, be utilized in a scenario in which there isno fiber (or other) connection available for Fixed APs (e.g., in amaritime scenario, in a plantation scenario, etc.), or in which a FixedAP is difficult to access or connect. For example, one or more MobileAPs of the mobile hotspot access network may be used as gateways toreach the Cloud. The fourth example mode 530 may also, for example, beutilized when a vehicle fleet and/or the Mobile APs associated therewithare owned by a first entity and the Fixed APs are owned by anotherentity, and there is no present agreement for communication between theMobile APs and the Fixed APs. Note also that the fourth example mode 530may be utilized in a scenario in which the fixed hotspot access networkis normally available but are currently unavailable (e.g., due toequipment failure, due to communication link failure, due to poweroutage, due to a temporary denial of service, etc.).

The fifth example mode (or configuration) 540 (e.g., a no mobilehotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without themobile hotspot access network and communication links therewith. Forexample, the communication system in the fifth example mode 540comprises a backbone provider network, a local infrastructure providernetwork, a fixed hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fifth example mode 540 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fifth example mode 540(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network, the fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wireless links. Note that thecommunication link(s) shown in the fifth example mode 540 of FIG. 5Bbetween the local infrastructure provider network and the fixed hotspotaccess network may be wired and/or wireless.

The fixed hotspot access network is also shown in the fifth example mode540 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fifth example mode 540 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fifth example mode 540 (e.g., the no mobile hotspots availablemode), information (or data) may be communicated between an end-userdevice and a server via the fixed hotspot access network, the localinfrastructure provider network, and/or the backbone provider network.As will be seen in the various example modes presented herein, suchcommunication may flexibly occur between an end-user device and a servervia any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc. For example, information communicated between anend user device and a server may be communicated via the localinfrastructure provider network, and/or the backbone provider network(e.g., skipping the fixed hotspot access network). Also for example,information communicated between an end user device and a server may becommunicated via the backbone provider network (e.g., skipping the fixedhotspot access network and/or local infrastructure provider network).

Similarly, in the fifth example mode 540 (e.g., the no mobile hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the fixed hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to the fixedhotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the fixedhotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the fixed hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network and/or the backboneprovider network).

In the fifth example mode 540, in an example implementation, theend-user devices and environment devices may communicate directly toFixed APs (e.g., utilizing Ethernet, Wi-Fi, etc.). Also for example, theend-user devices and/or environment devices may communicate directlywith the backbone provider network (e.g., utilizing cellularconnections, etc.).

The fifth example mode 540 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation in which end-user devices and/or environmentdevices may communicate directly with Fixed APs, such communication maybe utilized instead of Mobile AP communication. For example, the fixedhotspot access network might provide coverage for all desired areas.

Note also that the fifth example mode 540 may be utilized in a scenarioin which the fixed hotspot access network is normally available but iscurrently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The sixth example mode (or configuration) 550 (e.g., the no fixed/mobilehotspots and local infrastructure available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, fixed hotspot accessnetwork, mobile hotspot access network, and communication linkstherewith. For example, the communication system in the sixth examplemode 550 comprises a backbone provider network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the sixth example mode 550 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the sixth example mode 550 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links.

The end-user devices are also shown in the sixth example mode 550 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the sixth example mode 550 (e.g., the no fixed/mobile hotspots andlocal infrastructure available mode), information (or data) may becommunicated between an end-user device and a server via the backboneprovider network. Similarly, in the sixth example mode 550 (e.g., the nofixed/mobile hotspots and local infrastructure mode), information (ordata) may be communicated between an environment device and a server viathe backbone provider network. Also for example, an environment devicemay communicate with or through an end-user device (e.g., instead of orin addition to the mobile hotspot access network).

The sixth example mode 550 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, for example in which an end-user has not yetsubscribed to the communication system, the end-user device maysubscribe to the system through a Cloud application and by communicatingdirectly with the backbone provider network (e.g., via cellular link,etc.). The sixth example mode 550 may also, for example, be utilized inrural areas in which Mobile AP presence is sparse, Fixed AP installationis difficult or impractical, etc.

Note also that the sixth example mode 550 may be utilized in a scenarioin which the infrastructure provider network, fixed hotspot accessnetwork, and/or mobile hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The seventh example mode (or configuration) 560 (e.g., the no backboneand mobile hotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thebackbone provider network, mobile hotspot access network, andcommunication links therewith. For example, the communication system inthe seventh example mode 560 comprises a local infrastructure providernetwork, fixed hotspot access network, end-user devices, and environmentdevices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the seventh example mode 560 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the seventh example mode 560 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Note that the communication link shown inthe seventh example mode 560 of FIG. 5C between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the seventh examplemode 560 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Additionally, the end-userdevices are also shown in the seventh example mode 560 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the seventh example mode 560 (e.g., the no backbone and mobilehotspots available mode), information (or data) may be communicatedbetween an end-user device and a server via the fixed hotspot accessnetwork and/or the local infrastructure provider network. As will beseen in the various example modes presented herein, such communicationmay flexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network).

Similarly, in the seventh example mode 560 (e.g., the no backbone andmobile hotspots available mode), information (or data) may becommunicated between an environment device and a server via the fixedhotspot access network and/or the local infrastructure provider network.Also for example, an environment device may communicate with or throughan end-user device (e.g., instead of or in addition to the mobilehotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network) via any of a variety of differentcommunication pathways, for example depending on the availability of anetwork, depending on bandwidth utilization goals, depending oncommunication priority, depending on communication time (or latency)and/or reliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the local infrastructure provider network (e.g.,skipping the fixed hotspot access network).

The seventh example mode 560 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample controlled space implementation, Cloud access might not beprovided (e.g., for security reasons, privacy reasons, etc.), and full(or sufficient) coverage of the coverage area is provided by the fixedhotspot access network, and thus the mobile hotspot access network isnot needed. For example, the end-user devices and environment devicesmay communicate directly (e.g., via Ethernet, Wi-Fi, etc.) with theFixed APs

Note also that the seventh example mode 560 may be utilized in ascenario in which the backbone provider network and/or fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The eighth example mode (or configuration) 570 (e.g., the no backbone,fixed hotspots, and local infrastructure available mode) may, forexample, share any or all characteristics with the first example mode500, albeit without the backbone provider network, local infrastructureprovider network, fixed hotspot access network, and communication linkstherewith. For example, the communication system in the eighth examplemode 570 comprises a mobile hotspot access network, end-user devices,and environment devices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the mobile hotspotaccess network is shown in the eighth example mode 570 to becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Further, the end-user devices are alsoshown in the eighth example mode 570 to be communicatively coupled tothe environment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein.

In the eighth example mode 570 (e.g., the no backbone, fixed hotspots,and local infrastructure available mode), information (or data) mightnot (at least currently) be communicated between an end-user device anda server (e.g., a coupled to the backbone provider network, localinfrastructure provider network, etc.). Similarly, information (or data)might not (at least currently) be communicated between an environmentdevice and a server (e.g., a coupled to the backbone provider network,local infrastructure provider network, etc.). Note that the environmentdevice may communicate with or through an end-user device (e.g., insteadof or in addition to the mobile hotspot access network).

The eighth example mode 570 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the eighth example mode 570 may be utilized forgathering and/or serving data (e.g., in a delay-tolerant networkingscenario), providing peer-to-peer communication through the mobilehotspot access network (e.g., between clients of a single Mobile AP,between clients of respective different Mobile APs, etc.), etc. Inanother example scenario, the eighth example mode 570 may be utilized ina scenario in which vehicle-to-vehicle communications are prioritizedabove vehicle-to-infrastructure communications. In yet another examplescenario, the eighth example mode 570 may be utilized in a scenario inwhich all infrastructure access is lost (e.g., in tunnels, parkinggarages, etc.).

Note also that the eighth example mode 570 may be utilized in a scenarioin which the backbone provider network, local infrastructure providernetwork, and/or fixed hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

As shown and discussed herein, it is beneficial to have a genericplatform that allows multi-mode communications of multiple users ormachines within different environments, using multiple devices withmultiple technologies, connected to multiple moving/static things withmultiple technologies, forming wireless (mesh) hotspot networks overdifferent environments, connected to multiple wired/wirelessinfrastructure/network backbone providers, ultimately connected to theInternet, Cloud or private network infrastructure.

FIG. 6 shows yet another block diagram of an example networkconfiguration, in accordance with various aspects of the presentdisclosure. The example network 600 may, for example, share any or allcharacteristics with the other example networks and/or networkcomponents 100, 200, 300, 400, and 500-570, discussed herein. Notably,the example network 600 shows a plurality of Mobile APs (or OBUs), eachcommunicatively coupled to a Fixed AP (or RSU), where each Mobile AP mayprovide network access to a vehicle network (e.g., comprising othervehicles or vehicle networks, user devices, sensor devices, etc.).

In accordance with various aspects of the present disclosure, systemsand methods are provided that manage a vehicle communication network,for example in accordance with the location of nodes and end devices, ina way that provides for stable TCP/IP Internet access, among otherthings. For example, an end user may be provided with a clean and stableWi-Fi Internet connection that may appear to the end user to be the sameas the Wi-Fi Internet connection at the user's home, user's workplace,fixed public Wi-Fi hotspots, etc. For example, for a user utilizing acommunication network as described herein, a TCP session may stayactive, downloads may process normally, calls may proceed withoutinterruption, etc. As discussed herein, a vehicle communication networkin accordance with various aspects of this disclosure may be applied asa transport layer for regular Internet traffic and/or for privatenetwork traffic (e.g., extending the access of customer private LANsfrom the wired network to vehicles and users around them, etc.).

In accordance with an example network implementation, although a usermight be always connected to a single Wi-Fi AP of a vehicle, the vehicle(or the access point thereof, for example an OBU) is moving betweenmultiple access points (e.g., Fixed APs, other Mobile APs, cellular basestations, fixed Wi-Fi hotspots, etc.). For example, mobility managementimplemented in accordance with various aspects of the present disclosuresupports the mobility of each vehicle and its users across differentcommunication technologies (e.g., 802.11p, cellular, Wi-Fi, etc.) as theMobile APs migrate among Fixed APs (and/or Mobile APs) and/or as usersmigrate between Mobile APs.

In accordance with various aspects of the present disclosure, a mobilitycontroller (MC), which may also be referred to as an LMA or NetworkController, may monitor the location (e.g., network location, etc.) ofvarious nodes (e.g., Mobile APs, etc.) and/or the location of end usersconnected through them. The mobility controller (MC) may, for example,provide seamless handovers (e.g., maintaining communication sessioncontinuity) between different access points and/or differenttechnologies with low link latency and low handover times.

The architecture provided herein is scalable, for example takingadvantage of redundant elements and/or functionality to provideload-balancing of control and/or data communication functionality, aswell as to decrease failure probability. Various aspects of the presentdisclosure also provide for decreased control signaling (e.g., in amountand/or frequency), which reduces the control overhead and reduces thesize of control tables and tunneling, for example both in backendservers and in APs (e.g., Fixed APs and/or Mobile APs).

Additionally, a communication network (or components thereof) inaccordance with various aspects of this disclosure may comprise theability to interact with mobile devices in order to control some or allof their connection choices and/or to leverage their controlfunctionality. For example, in an example implementation, a mobileapplication can run in the background, managing the available networksand/or nodes thereof and selecting the one that best fits, and thentriggering a handoff to the selected network (or node thereof) beforebreakdown of the current connection.

The communication network (or components thereof) is also configurable,according to the infrastructure requirements and/or mobility needs ofeach client, etc. For example, the communication network (or componentsthereof) may comprise the capability to support different Layer 2 (L2)or Layer 3 (L3) implementations, or combinations thereof, as well asIPv4/IPv6 traffic.

There is an ever growing amount of data generated throughout the hugevariety of connected devices in the network of moving things. Aspects ofthis disclosure provide for cost-effective retention and disseminationof such data through the vehicular network infrastructure, while meetingthe QoS needs of the applications/services that use such data. Suchapplications/services may be located in the Cloud, may be provided bynetwork nodes (e.g., mobile or fixed access points (MAPs or FAPs), ormay be run by the end-user devices connected to the APs. As used herein,“data retention and dissemination rules” may be used to govern where(i.e., in which network nodes and/or which storage devices of whichnetwork nodes), when (i.e., at what times and/or for how long), and/orhow (i.e., in what format or form of organization (e.g., compressed,non-compressed, structured as “objects”, unstructured files, etc.), viawhich type(s) of network communication link(s) (e.g., Wi-Fi (e.g., IEEE802.11a/b/g/n/ac/ad/ad), cellular (e.g., 3G, 4G, LTE, GSM, CDMA, etc.))data is: routed, stored, dropped, replicated, shared, prioritized,scheduled, and/or the like, in the upstream and/or downstreamdirections. As used herein, the term “bundle” may be used to refer to ablock/package/unit of data (e.g., comprising one or more fragments ofdata from one or more files from one or more sources) sent between afirst network node and a second network node. A bundle may consist of asingle packet (e.g., an IP packet) or may be a set of such packets thatbelong to the same piece of data. It should be noted that while thelength of a packet may, for example, be defined in terms of a MaximumTransfer Unit (MTU) number of bytes (e.g., 1500 bytes in some networks),a bundle may be made up of one or more packets, depending upon theamount of data to be transferred from the sending network node toreceiving network node. In accordance with various aspects of thepresent disclosure, a bundle may be split at the sending node andaggregated again at the receiving node.

The highly mobile and constantly changing nature of mobile APs can makeit difficult to communicate large amounts of data to and from the mobileAPs in a timely and cost-efficient manner. Accordingly, various aspectsof this disclosure enable taking advantage of the intermittent contactsthat may occur among mobile APs and between mobile APs and fixed APs, inorder to reduce the cost of storing and transferring the data. By takingadvantage of aspects of this disclosure, the data can be better balancedamong mobile APs, thus reducing the amount of storage capacity requiredof the mobile APs, while still meeting latency/QoS requirements of theend-users of the data and reducing reliance on expensive (e.g.,cellular) data connections. For example, in prior art networks, a mobileAP that does not frequently connect to any fixed APs may be forced toresort to, for example, a cellular data connection to enable the mobileAP to reach a resource or system located in, for example, theCloud/Internet. Aspects of the present disclosure, however, enables suchmobile APs to communicatively couple to other mobile AP(s) thatmore-frequently connect to one or more fixed AP(s), thus enabling thoseAPs to reach the Internet/Cloud without having to resort to a morecostly (e.g., cellular) data connection.

Aspects of this disclosure provide various methods and systems that maybe used to optimize (e.g., in terms of overhead such as cellular networkusage, amount of network congestion introduced, number of dataconnections established, etc.) the flow of data between mobile APs bothin the upstream and downstream directions.

In an example implementation, a sending node of a network as describedherein (e.g., a mobile AP) may broadcast a bundle to be received by oneor more neighboring nodes of the network (e.g., MAPs and/or FAPs withincommunication range of the sending MAP). Each of those neighboring nodesmay then decide, based upon context information available to therespective neighboring node, whether or not to store the receivedbundle, and whether or not to acknowledge the receipt of the bundle tothe sending node.

In accordance with aspects of the present disclosure, the sending mobileAP may decide, based on context information available to the sendingMAP, whether or not to replicate a bundle to one or more of itsneighboring nodes using, for example, unicast messages (addressed to asingle receiver), and if so, whether or not to wait for acknowledgementof the unicast message by the neighboring node. Thus, in such animplementation, the decision/knowledge regarding how to handle thebundle is centralized at the sender.

In a network according to aspects of the present disclosure, one or morenodes of the network (e.g., devices such as mobile APs, fixed APs, DelayTolerant Network/Disruption Tolerant Network (DTN) servers, etc.) mayadvertise information about one or more bundles that the one or morenetwork nodes are currently storing (e.g., by sending unicast,multicast, and/or broadcast messages into the network). Such advertisedinformation may include, for example, the type of data in the bundle(s),the size of the bundle(s), whether the network node is trying to sendthe bundle(s), the destination of the bundle(s), etc. Other networknodes receiving such advertisements may then use context informationavailable to the other network nodes to decide whether the other networknodes want/need the bundle(s), and/or whether the other network nodescan accept receipt of the bundle(s) for subsequently forwarding to yetanother network node.

In accordance with various aspects of the present disclosure, one ormore nodes of the network (e.g., devices such as mobile APs, fixed APs,DTN servers, etc.) may advertise information about one or more bundle(s)that they are currently in need of or want to receive (e.g., by sendingunicast, multicast, and/or broadcast messages into the network). Othernetwork nodes receiving such advertisements may then use contextinformation available to the other nodes to decide whether they are inpossession of the wanted/desired bundle(s), and, if so, whether theother nodes can and/or should agree to deliver the bundles to the nodeadvertising the need/want.

In a network according to aspects of the present disclosure, networknodes (e.g., mobile APs or other devices) may establish what may bereferred to herein as a “control channel” with one or more fixed APsand/or the Cloud, in order to gather context information that may beused in selecting and implementing data dissemination and retentionrules.

In a network as described herein, for communication in the “upstream”direction (i.e., in which the Internet/Cloud is the end destination),many or all of the nodes of the network may attempt to send data to thesame destination (e.g., DTN server), whereas communication in the“downstream” direction (i.e., from the Internet/Cloud to the APs) mayinvolve the use of “flooding” mechanisms to distribute data to the nodesof the network. Accordingly, in such a network, a first set of one ormore data dissemination and retention rules may be used for the“upstream” communication, and a second, possibly different, set of oneor more data dissemination and retention rules may be used for“downstream” communications. Such data dissemination and retention rulesmay be a part of configuration information distributed to the nodes of anetwork according to the present disclosure. Additional informationabout the distribution of such configuration information may be found,for example, in U.S. patent application Ser. No. 15/138,370, titled“Systems and Methods for Remote Configuration Update and Distribution ina Network of Moving Things,” filed Apr. 26, 2016, the complete subjectmatter of which is hereby incorporated herein, in its entirety.

In a network according to various aspects of the present disclosure, thecontext information used by a particular network node at any particulartime may comprise, by way of example and not limitation, characteristicsof the particular node (e.g., the network or geographic location, speed,direction, path of travel, uptime, hardware configuration, softwareconfiguration, and/or the like); characteristics of data to be sent orreceived by the particular node (e.g., the size, QoS requirements,and/or the like); and/or characteristics of any wireless link(s)available for communicating the data (e.g., maximum available bandwidth,currently available bandwidth, amount of congestion, error rate, etc.).The context information used by the particular network node may alsocomprise, for example, characteristics of neighbor device(s) such as,for example, the speed, direction, and/or path of travel of eachneighbor; the type and/or amount of data storage available on eachneighbor; an operator of each neighbor; and/or the like, where theneighbor(s) may comprise one or more mobile APs, fixed APs, cellularbase stations, and/or end-user devices. In addition, the contextinformation used by the particular network node may comprise, by way ofexample and not limitation, characteristics of the environment of theparticular network node such as, for example, a number/density of nodespresent within a determined region or area surrounding the network node;an amount of wireless interference or activity present in an area aroundthe network node; the presence/size/location/etc. of physicalobstructions that may affect the particular network node (e.g., whetherline-of-sight vs. non-line-of-sight communication is possible); and/oran expected time until being in-range of a fixed AP, and/or the like).

In accordance with various aspects of the present disclosure, suchcontext information may be provided by, for example, devices in theInternet/Cloud, mobile APs of the vehicular network, fixed APs of thevehicular network, sensors of the vehicular network, and/or end-userdevices of the vehicular network. For example, one or more of thesenetwork nodes and/or devices may probe the network and may providecontext information in real time.

As a few, non-limiting examples, context information used by aparticular node for a particular bundle may comprise the number ofreplicas of the particular bundle that currently exist in the network; aprobability that the particular node can wirelessly communicate with aparticular neighbor node (e.g., without using a cellular connection); aprobability that the particular node can communicate with any neighbornode; and/or a probability that the particular node will be at or inproximity to a particular geographic location within some determinedtime interval (e.g., for nodes that are mobile). Context informationused by the particular node for a particular bundle may also comprise,for example, a probability that the particular node will be able towirelessly connect to a fixed AP (e.g., based on its current geographiclocation, historical information of the geographic location of theparticular node, and/or the geographic location(s) of one or more fixedAPs of the network). In addition, context information used by theparticular node for a particular bundle may also comprise, for exampleamount of unused storage in the particular node; an amount of unusedstorage in one or more neighboring nodes; a number of missing fragmentsof a specific file that are needed in order to decode the entire file; a“time-to-live” for the particular bundle; a latency tolerance of theparticular bundle; a number of hops the bundle has traversed and/orshould traverse; and/or a past, present, and/or predicted future numberof nodes that have been/are/will be neighbor nodes of the particularnode. The term “time-to-live” may be used herein to refer to a maximumamount of time that a bundle is allowed to be in transit within thenetwork before an action is taken to delete the bundle from each node ofthe network. In accordance with various aspects of the presentdisclosure, a bundle may, for example, contain a “date/time of creation”(e.g., 15:30 02/02/17 UTC) and a “time-to-live” (e.g., 3600 seconds or60 minutes). In an alternate instance according to the presentdisclosure, each bundle may, for example, contain a “date-to-live” or“expiration date” (e.g., 16:30 02/02/17 UTC), which may define adate/time when the bundle is no longer valid. Using such information, anetwork node (e.g., a mobile AP, fixed AP, NC, sensor, etc.) maycalculate, using current date/time information from, for example, aGNSS/GPS receiver or a Network Time Protocol (NTP) server, whether thebundle is valid. In accordance with aspects of the present disclosure, a“time-to-live” or “date-to-live” may provide for a bundle life of, forexample, up to 60 seconds, up to an hour, or as much as a day.

Various aspects of this disclosure enable prioritizing and/or schedulingcommunication and/or delivery of a bundle based on a “time-to-live” ofthe bundle, an indication of priority and/or importance of the bundle,an indication of latency sensitivity of the bundle, and/or othercharacteristics of the bundle. A network in accordance with aspects ofthe present disclosure includes methods and systems for schedulingbundles carrying real-time data that is to be communicated with highestpriority.

Various aspects of the present disclosure provide methods and systemsfor dealing with a variety of characteristics of different types ofstorage systems which may be in use at the nodes (e.g., FAPs, MAPs, NCs,sensor(s)) of the network. By way of example and not limitation, thecontext information may include storage capacity, read/write speed,organization, etc. of storage devices and file systems from which thedata will be read and/or to which the data will be stored. For example,some storage systems of a network node may comprise hard disk drives,and some may comprise solid state devices (e.g., FLASH-based or batterybacked RAM). Some storage in network nodes may, for example, beorganized as file-based storage, some may be organized as object-basedstorage, and some may use other types of organization/structure.

In accordance with various aspects of the present disclosure, datacompression may be applied to a particular bundle at a particular time,and the algorithms for such data compression may be determined based oncontext information. For example, the data compression algorithmemployed, the target compression ratio, and other aspects, may bedetermined based on the type of data contained in the bundle. By way ofexample and not limitation, the data contained in a bundle may becharacterized by metadata such as a file extension that associates thedata with a particular software application, by latency sensitivity ofthe bundle, by a “time-to-live” of the bundle, by a type of networkconnection over which the bundle is to be communicated, to name only afew characteristics that are contemplated.

In a network according to aspects of the present disclosure, contextinformation may be used to determine which bundles a network node (e.g.,FAPs, MAPs, NCs, etc.) is to drop/delete/overwrite in order to maintaina sufficient quality of service (QoS). Whether a particular network nodestores or drops a particular bundle may depend upon, by way of exampleand not limitation, one or more indicators of the urgency,delay-sensitivity, loss-tolerance, and/or “time-to-live” of the bundle;an amount of bandwidth available on communication links to/from thenetwork node currently handling the bundle, and/or an amount or type ofstorage available in the node handling the bundle. In addition, if adecision is made to store the particular bundle at the particular node(e.g., based on any of the context information discussed herein), theduration of time for which the particular bundle should be stored at theparticular node may be determined based on any of the contextinformation described herein.

A node of a network according to aspects of the present disclosure(e.g., a fixed AP, mobile AP, network controller) may, for example, beconfigured to predict the impact of various possible data disseminationand retention rules, to assess which rule(s) will be the best, or atleast a suitable choice. Such a prediction may be based, for example, oncontext information advertised by the Cloud, by fixed APs, by mobileAPs, by sensors, and/or by end-user devices. In accordance with someaspects of the disclosure, such predictions may be based on contextinformation collected and/or derived from previous surveys and/oranalyses performed in a network context similar to the context that amobile AP is currently experiencing, or may be predicted to experiencein the near term. Some example characteristics used in making suchpredictions may include, by way of example and not limitation, a networkor geographic location, a measure of density of mobile APs, a measure ofdensity of fixed APs, obstructions that may impact wirelesscommunication, requirements set by the end-users of the data beingcommunicated, to name just a few.

Methods and systems in accordance with aspects of this disclosure mayuse hysteresis and/or other techniques to reduce frequency of switchingbetween different data retention and dissemination rules, so as to avoidoscillations that may occur between different rules, and to reduce anycomputational and/or resource costs of managing the data disseminationand retention rules. For example, switching to a different dataretention and dissemination rule may involve arriving at a consensus ofa defined set of nodes (e.g., one or more nodes in the same geographicregion or same cluster).

Aspects of this disclosure enable gathering data from multiple andheterogeneous sources in a network of moving things, while taking intoaccount the limited resources (e.g., CPU computing capacity, datastorage capacity and types, operating power, etc.) of many of the nodesthat are part of the network, to ensure that software applications thatuse the gathered data receive it in accordance with their QoSexpectations. Aspects of this disclosure provide a network that isscalable, reliable, and that provides high-performance support for thegathering, transportation, dissemination, and sharing of informationamong different network elements, while ensuring selection of suitabletrade-offs between the various requirements of all the softwareapplications and services that make use of such data.

In a network as described herein, data storage/retention anddissemination rules may comprise various parameters which may bedynamically configured/adapted. Changing one or more such parametervalues is referred to herein as changing the data storage/retention anddissemination rule or switching between different data storage anddissemination rules. As previously noted, a network in accordance withaspects of the present disclosure may have multiple sets of datastorage/retention and dissemination rules for communication of datatraffic in “upstream” and “downstream” directions. Some examples of suchparameters include, but are not limited to, a maximum number of replicas(i.e., copies) that should be generated for a bundle at a network node,a maximum number of hops (i.e., communication paths or links) onto whichto replicate a particular bundle, priorities of various data types,priorities of various senders of bundles, priorities of variousrecipients of bundles, whether or not a recipient of a bundle is to sendan acknowledgement (ACK) of receipt of the bundle, and whether a node isto use broadcast, multicast, and/or unicast in communicating a bundle.

FIG. 7 shows a block diagram of an example mobile AP 701 in a network ofmoving things 710, in accordance with various aspects of the presentdisclosure. In the example shown in FIG. 7, the mobile AP MAP 1 701 isconfigured to communicate with a delay tolerant networking (DTN) server720 and a set of application programming interfaces 732 of a Cloud 730,to implement data retention and dissemination rules as described herein.Functionality (e.g., circuitry, logic, and/or executable instructions)supporting delay tolerant networking in accordance with this disclosuremay, for example, be integrated into one or more APs (e.g., mobile APsand/or fixed APs) or other nodes of the network 710 including, forexample, one or more Cloud-based servers (e.g., the DTN server 720 shownin FIG. 7). The MAP 1 701 of the network 710 is also communicativelycoupled to a sensor 1 702 and sensor 2 703, a fixed AP FAP 1 706, andmobile APs MAP 2 704 and MAP 3 705. In the example arrangement of FIG.7, the functionality of the DTN server 720, the mobile APs MAP 1 701,MAP 2 704, and MAP 3 705; and the fixed AP FAP 1 706 manage andimplement data storage and dissemination rules for the upstream transfer(i.e., “uploading”) of data from the APs (e.g., the FAP 1 706, MAP 1701, MAP 2 704, and MAP 3 705) to the DTN server 720, and for the“downstream” transfer (i.e., “downloading” or distribution) of data fromthe DTN server 720 to the APs (e.g., the FAPs and MAPS). For example, inaccordance with various aspects of the present disclosure, the DTNfunctionality of the mobile AP MAP 1 701 of FIG. 7 may, for example, befed with context information from the current neighbors of the mobile APMAP 1 701 (i.e., FAP 1 706, MAP 2 704, MAP 3, Sensor 1 702, and Sensor 2703), and with context information from the Cloud and the DTN server720.

FIG. 8 shows a block diagram of example delay tolerant networkingfunctionality 800 for implementing data retention and disseminationrules of nodes of a network of moving things, in accordance with variousaspects of the present disclosure. The DTN functionality 800 illustratedin FIG. 8 comprises an API functional block 810, a receive functionalblock 811, a storage functional block 812, a neighboring functionalblock 813, a routing functional block 814, and a context informationfunctional block 815. It should be noted that the functionality of thevarious blocks of FIG. 8 may be realized in hardware/circuitry,executable instructions/software code, logic, and/or any combination ofthe above.

The neighboring functional block 813 of FIG. 8 is configured to maintainan updated list of all neighbor nodes of the network node containing thefunctionality of FIG. 8. Such a list of neighbor nodes may contain dataitems/entries for each neighbor node, where the data items/entries foreach neighbor node may include any of the context information discussedabove with respect to neighbor nodes. For example, such a list entry fora neighbor node may include, by way of example and not limitation, thetype of the neighbor node (e.g., FAP, MAP, Sensor, NC, etc.); thegeographic location of the neighbor node (e.g., latitude/longitude); thespeed, direction, and/or a path of travel of the neighbor node (i.e.,for neighbor nodes that are MAPs); as well as other context informationsuch as a received signal strength indication (RSSI) for the neighbornode. The neighboring functional block 813 may interact with, forexample, an operating system of the node in which the functionality ofFIG. 8 resides, to obtain information about the available neighbors ofthe node, such as mobile and fixed APs, Wi-Fi neighbors, or neighbors inother technology (e.g., Bluetooth, DSRC, etc.).

The receive functional block 811 is configured to receive and processincoming bundles (i.e., via In 820) from other nodes of the network. Thereceive functional block 811 may interact with the storage functionalblock 812 to store received bundles and characteristics about the storedbundles, and to access characteristics about the stored bundles. Suchcharacteristics may include those described herein such as, for example,the size of the bundle, metadata such as a file extension thatassociates the data of the bundle with a particular softwareapplication, a type of data of the bundle, a latency sensitivity of thebundle, a “time-to-live” of the bundle, and a type of network connectionover which the bundle is to be communicated, to name just a fewcharacteristics. Such stored characteristics may be accessed for thepurpose of creating acknowledgements (ACKs) and/or other messages (e.g.,a response indicating that the data of the bundle was previouslyreceived, a response indicating that the storage for bundles at the nodeis full, etc.), regarding the received and/or stored bundles. Thereceive functional block 811 may, for example, implement data retentionrules that are used to determine which received bundles are to be storedin the storage functional block 812.

The routing functional block 814 is configured to generate and sendmessages to other nodes of the network. The routing functional block 814may, for example, interact with neighbors of a network node (e.g., nodeswithin wireless communication range of the node in which the routingfunctional block 814 resides), to acquire and maintain updatedinformation about the current neighbors of the node, and may interactwith the storage functional block 812, to “peek” a bundle. The term“peek a bundle” may be used herein to refer to an action by a networknode (e.g., a fixed or mobile AP, NC, sensor, etc.) to, for example, getaccess to or a copy of a bundle, or access to or a copy of the headersof a bundle (e.g., from storage), to enable the network node todetermine using the information in the bundle, when, where, and to whomto send the bundle. The routing functional block 814 may be configuredto implement data dissemination rules used to determine, by way ofexample and not limitation, which received bundles are to be sent, whichnode(s) are to receive the bundles that are sent, the communicationlink(s) (e.g., Wi-Fi, DSRC, Bluetooth, cellular) to be used for sendingthe bundles, the settings to be used on the communication link(s) (e.g.,the data rate, the modulation scheme, any time-out values, maximumnumber of retries, etc.) to be used when sending the bundles, etc. Therouting functional block 814 of a node may, for example, operate todefine data storage and dissemination rules related to one or moreconditions in which bundles are dropped by the node, and howprioritization and scheduling of the transmission of bundles is done bythe node. Such rules may, for example, provide for multiple classes ofservice in regards to bundle delivery delay and loss tolerance.

The storage functional block 812 is configured to maintain a datastructure having records/entries for all bundles received by the node(e.g., organized in different lists, organized by a type of storagedevice used to store the bundle (e.g., a memory card (e.g.,SD/SDHC/SDXC, CF, etc.), system FLASH memory, battery-backed RAM, and/orother forms of data storage). The storage functional block 812 mayinteract with the receive functional block 811 and the routingfunctional block 814, to provide access to, to retrieve, and/or to storedata, as well as other functions that may be used to collect/generatecontext information.

The context information functional block 815 is configured to collectinformation from the neighbors of a node, from a remote server (e.g.,the DTN server 720 of FIG. 7), and from the Cloud. The routingfunctional block 814 and the receive functional block 811 may then usethe context information to configure and implement data storage anddissemination rules.

The application programming interface (API) functional block 810 of anetwork node is configured to parse instructions, referred to herein as“API calls,” that are received by the node via the receive functionalblock 811. The API functional block 810 may then validate and/orauthenticate the received API calls, and may then perform or cause theperformance of operations requested by valid and/or authenticated APIcalls. Such API calls may include, for example, an API call to storedata to the storage functional block 812, and an API call to fetch datafrom the storage functional block 812 for transmission via the routingfunctional block 814.

In an example implementation in accordance with various aspects of thepresent disclosure, control communications among network nodes (e.g.,mobile APs, fixed APs, and a DTN server) may use a short “common header”for all types of messages, and may use a “type-specific header” thatfollows the “common header.” Such type-specific headers may include, forexample, what may be referred to herein as a “bundle header” (e.g., aheader specifically used for messages carrying data being disseminated),what may be referred to herein as an “ACK header” for use in anacknowledgment message, and other type-specific headers for various“control messages.”

The term “control message” may be used herein to refer to any type ofpacket used to communicate information/context between/among two or morenetwork entities including, for example, one or more MAPs, FAPs, DTNserver(s), sensor(s), and/or the Cloud. A control message may be a“request control message” that may be used, for example, to request anytype of information from one or more other node(s), or a “responsecontrol message” that may be used to provide a response to a requestfrom another node. For example, a “response control message” may be usedto provide context information about status of particular bundles, aboutthe probability of being within range of wireless communication (e.g.,“contact”) with a particular network node, and/or about the presence ofnew bundles in a network in accordance with various aspects of a networkof moving things as described herein.

In a network in accordance with aspects of the present disclosure, an“ACK message”, as well “response control messages” or any type of“control message” may include space for one or more “flags.” Such flagsmay be used by a receiving node to provide additional information aboutthe status of delivery of a control message, as well as the status ofthe responding neighbor, to the sending node. Examples of such statusinformation include, but are not limited to, whether storage at theneighbor is full, whether the neighbor is experiencing any sort oftechnical problem(s), whether the neighbor accepts custody of the datajust sent to the neighbor, whether the neighbor received and stored thedata just received, whether a sufficient number of data fragments areavailable to enable reconstruction of the file of which the data is apart, and whether the data sent to the neighbor was already stored atthe neighbor.

In an example implementation according to aspects of the presentdisclosure, the neighboring functional block 813 may provide contextinformation including, for example, updates on the state of neighboringnodes. Such context information may be real-time context information, inthat such information may reflect the state of a neighbor node within ashort period of delay (e.g., within millisecond, tens of milliseconds,or a few hundred milliseconds of existence of the state at the neighbornode). In accordance with aspects of the present disclosure, changes ina list of neighbors maintained by any given network node (e.g., locatedin an operating system Kernel of the node) may be announced to the DTN.Such an announcement of changes may be sent to any network node thatbelongs to the DTN including, for example, neighbor nodes, neighbors ofneighbor nodes, and a DTN server. In accordance with aspects of thepresent disclosure, the neighboring functional block 813 of any networknode may pre-filter the list of neighbors that the node maintains. Thepre-filtering may be performed before the list of neighbors of the nodeis announced to the DTN. Such pre-filtering may, for example, be basedon context information maintained by the node including, by way ofexample and not limitation, RSSI measurements of wireless signal(s) fromthe neighbor node(s), an average time between reboots of the neighbornode(s), an indication of one or more technical (e.g., electrical,software, etc.) problem(s) at the neighbor node(s), and/or otherinformation that is a factor in assessing the reliability or stabilityof the neighbor node(s). Such pre-filtering may produce a list of the“best” or “healthiest” neighbors, which may identify those neighborsthat may be relied upon to operate predictably and reliably. In thismanner, the routing functional block 814 of a node may then use thefiltered list of neighbor nodes in configuring and implementing datastorage/retention and dissemination rules. In accordance with variousaspects of the present disclosure, one or more thresholds for one ormore parameter values used in the pre-filtering process (e.g., a minimumRSSI for a node to be considered as providing a usable wirelesscommunication link) may be adjusted dynamically, based on a variety offactors including, for example, feedback from previous communicationwith neighbor nodes, the size of a particular bundle to be transmittedto a neighbor node, and/or the like.

In accordance with aspects of the present disclosure, datastorage/retention and dissemination rules for upstream data maydetermine, by way of example and not limitation, whether a bundle issent as unicast or broadcast traffic; whether a recipient of the bundleis to send an ACK; and/or whether an end-to-end ACKs for a bundle is tobe sent to and/or from a DTN server (e.g., DTN server 720). Such datastorage/retention and dissemination rules for upstream data may alsodetermine, for example, how many replicas/copies of a particular bundleshould be sent by a particular sender or a particular type of sender(e.g., the sender originating the bundle and communicating the bundle toan intermediate node, an intermediate node communicating the bundle toanother intermediate node, a sender communicating the bundle to a DTNserver, and/or other types). Data storage/retention and disseminationrules for upstream data of a network, in accordance with aspects of thepresent disclosure, may determine, by way of example and not limitation,whether to use fixed access points as anchors (i.e., whether a mobile APshould only send or receive a bundle that originated at a fixed AP, whenin range of a fixed AP). Such data storage/retention and disseminationrules for upstream data may also determine, by way of example and notlimitation, whether to request control information from fixed APs and/orthe Cloud, to help the upload of a particular file (e.g., informationabout how many more fragments are needed to be able to decode theparticular file, how many fragments of a particular file have beenreceived so far, and/or the like); and/or whether a device, or a bundleis currently on, or should be added to, a “blacklist.” The term “device”may be used in this context to refer to, for example, a network node(e.g., a fixed or mobile AP, NC), an end-user device (e.g., a cellphone;smart phone; tablet, laptop, or other type of computer), or a sensor, ifsuch a device is part of a DTN. In accordance with aspects of thepresent disclosure, a “blacklisted” device or node may not be used tosend bundles, and may be avoided by other network nodes, etc., since thedevice or node may be “blacklisted” for many reasons including, forexample, poor network performance, full/limited storage capacity, and/orsecurity issues, to name only a few reasons.

FIG. 9 is a high-level flowchart 900 illustrating an example process formanaging data storage/retention and dissemination of a bundle in theupstream direction, in accordance with various aspects of the presentdisclosure. In block 902, an upstream bundle is generated or received bya device of the network of moving things. In various scenarios, thedevice referred to in FIG. 9 may be a mobile AP, a fixed AP, or anend-user device. In block 904, the device determines which action(s) totake with the upstream bundle (e.g., whether to store it, forward it,replicate it, drop it, and/or the like) based on context informationavailable to the device. In block 906 the device performs the action(s)determined in block 904.

At block 904, the method of FIG. 9 may comprise, for example, decidingwhether to forward/send the bundle and, if so, whether to send it in aunicast message to a single neighbor node, or whether to broadcast ormulticast it to multiple neighbor nodes. In accordance with aspects ofthe present disclosure, context information which may be used to makethis decision includes, by way of example and not limitation, whetherand/or how many “one-hop neighbors” are available to the node, the RSSIfor each such neighbor node, the storage capabilities of each suchneighbor node, and/or the number of replicas/copies of the bundle thathave already been communicated by the device and/or by other devices.

An advantage of sending the bundle in one or more unicast transmissionsis that sending one or more unicast transmissions enables finer controlof how many replicas/copies of the bundle are disseminated throughoutthe network, reducing the burden on other nodes which would have todemodulate/decode a broadcast message that may not be relevant to theother nodes. A disadvantage of sending the bundle in one or more unicastmessages is that doing so fails to take advantage of the promiscuousnature of the wireless medium used for communication. One examplescenario in which a network node (e.g., a device such as a MAP, FAP, NC,etc.) may decide to send a bundle in one or more unicast messages, iswhere there is a large number of neighbor nodes in the network (i.e., areally high vehicle density (e.g., more than 10, more than 20, or morethan 30 nodes/vehicles a members of a DTN)), but there are relativelyfew (e.g., only one or a few) node(s) that has/have a much higherlikelihood than other node(s) of successfully delivering the bundle.Using this approach, replication of the bundle may be more accuratelycontrolled than broadcasting the bundle into a crowded environment(possibly worsening network congestion, etc.).

An advantage of broadcasting a bundle is that several replicas of thebundle are shared in a single transmission. That is, a bundle that isbroadcast is a single physical transmission by the source node that isshared with multiples recipients. It should be noted that, although onlya single bundle is physically transmitted by the source node, multiplecopies of the bundle may be distributed throughout the DTN at nodes thataccepted the bundle that was broadcast. Another advantage is that thesender may avoid implementing resource-intensive data disseminationrules to decide to which node(s) the bundle should be replicated. Adisadvantage of broadcasting the bundle is that there is less controlover how many replicas of the bundle get shared than when, for example,a bundle is sent using one or more unicast transmissions. It should benoted, however, that it is possible to control the number of broadcasttransmissions in a network in accordance with various aspects of thepresent disclosure. One example scenario in which a node may decide thata bundle is to be broadcast is when there is a high density of networknodes (e.g., MAPs of vehicles), so that the sender can make use of thesame transmission to reach multiple destination nodes. In accordancewith aspects of the present disclosure, a sending node may decide tobroadcast a particular bundle when, for example, the sending node knowsthat all/most of the neighbor nodes have at least a certain thresholdamount of storage space still available in which to store the bundle.Such a storage space requirement may be mandatory, or may be overriddenwhen, for example, one or more characteristics of the particular bundleindicate that the priority or importance of delivery of the bundle tothe nodes of the network is at or above a certain threshold.

At block 904, the method of FIG. 9 may comprise, for example, decidingwhether to send an ACK message in response to receipt of a bundle and,if so, whether to send one or more unicast ACK messages or to send abroadcast ACK message. An advantage of not sending an ACK is that itreduces congestion on the wireless medium. A disadvantage of not sendingan ACK is that the sending node does not know the status of the bundleand whether it was successfully received by the destination node(s). Thefailure to employ an ACK message may lead to the transmission ofunnecessary replicas of the bundle. In accordance with various aspectsof the present disclosure, a network node may decide to not send an ACKmessage for a received bundle when the wireless medium used forcommunication is overloaded (e.g., in areas with high node density). Anoverload condition may be considered to exist when, for example,utilization or occupancy of the wireless medium being used by the senderis above one or more certain thresholds. A network node may also decideto not send an ACK message for a bundle when, for example, one or morefixed APs are within a certain distance proximity to the sender of thebundle and/or receiving signals above one or more thresholds indicatingwireless communication with the sender is available, because the sendermay be able to get information about the bundle from the Cloud, when thesender is directly connected, via a wireless network, to the fixed AP.

An advantage of a recipient node sending an ACK message is that the ACKmessage may, for example, provide information such as an amount ofstorage currently available at the recipient node, a notification thatthe sender may delete the bundle because the recipient node is acceptingcustody of it, a notification that the recipient node already had a copyof the bundle in storage at the recipient node, and/or a notificationthat enough fragments of a file, part of which may be contained in thebundle, have now been received to enable reconstruction of the entirefile. An advantage of sending a unicast ACK (e.g., as opposed to abroadcast ACK) is that only the recipient of the ACK (i.e., the senderof the bundle) received and therefore may need to process the ACK. Oneexample scenario in which a network node may decide to send a unicastACK is when the sending and/or receiving nodes do not often come withinrange of a fixed AP, and thus storage of the bundle would be too large astorage burden for the node to store all received/generated bundlesuntil a fixed AP is in communication range. Another example scenario inwhich a recipient node may decide to send a unicast ACK is when the RSSIof the wireless signal from the sender as measured at the recipient iswithin a range of RSSI values in which successful delivery of a bundleis uncertain, as opposed to RSSI values below such a range, wheredelivery is likely to fail, or RSSI values above such a range, wheredelivery of a bundle is likely to succeed. An advantage of sending abroadcast ACK is that all neighbors of the sender become aware of thewireless communications in their area or region, and the status ofvarious bundles being communicated. One example scenario in which anetwork node according to the present disclosure may decide to send abroadcast ACK, is where the nodes of a group of nodes (e.g., mobile APs)are within wireless communication range of one other (i.e., may beneighbor nodes of one another) for at least a certain amount of time,and are also within wireless communication range of a fixed AP. In thisscenario, sending an ACK as a broadcast transmission may enable thenodes of the group to learn which of the other nodes in the group havealready received particular bundle, and thereby reduce unnecessarytransmissions of the bundle among the group of nodes.

As used herein, the term “end-to-end (E2E) ACK” may refer to an ACK sentby a DTN server (e.g., DTN server 720) that indicates that a completefile, or enough parts of the file so that the complete file can bereconstructed, has been received by the DTN server. At block 904, themethod of FIG. 9 may comprise, for example, a DTN server (e.g., DTNserver 720) deciding whether to send an E2E ACK, and, if so, whether todisseminate the E2E ACK via mobile APs, fixed APs, or a mix. Anadvantage of not sending an E2E ACK is that not sending an E2E ACKavoids placing additional load on the communication network. One examplescenario in which a DTN server may decide to not send an E2E ACK is whenbundle dissemination rules are such that a burdensome number ofunnecessary replicas are not likely to be sent. Another examplescenario, in which a DTN server may decide to not send an E2E ACK iswhere a file is small, is able to be contained in a single bundle, andthe source of the bundle used to carry the file is the network node thatdelivers the entire file.

In accordance with various aspects of the present disclosure, a DTNserver (or any other node that is a final destination of a bundle) maysend an E2E ACK back to the source node. Sending an E2E ACK introducesmore load upon the DTN, as the E2E ACK is similar to a data packet,albeit of a possibly smaller size. The E2E ACK is, however, important tothe source node and other network nodes in the path from the destinationnode to the source node to, for example, enable the source node to stopsending packets/fragments from the current bundle, and also to enableother network nodes along the path to be able to delete the bundle fromthe storage of the other network nodes. The network node that is thefinal destination of a bundle may, for example, consider a number offactors before sending an E2E ACK including, by way of example and notlimitation, the size of the full bundle, how close the current time isto the bundle expiration date/time, the receive data rate of the currentbundle, and the likely distance (e.g., in hops) from the sender of theE2E ACK, to the source node.

An advantage of sending an E2E ACK is that the network node that is thesource of the bundles that contain a particular file may be notifiedthat the entire file has arrived at the destination node, and that thesource node is then able to update its replication/storage strategiesaccordingly. For example, in such a situation, a source node may stopsending replicas of the bundle(s) and/or drop the bundle(s) that containa file. An advantage of sending E2E ACKs using fixed APs as anchors isthat the use of such an approach may avoid the utilization of resourcesrequired for disseminating the E2E ACKs via the mobile APs. Adisadvantage of sending E2E ACKs when using fixed APs as anchors is thatsuch an approach may involve extra coordination between the source nodeand a DTN server when the source is near a fixed AP, and may involveadditional processing at the DTN server. An advantage of disseminatingE2E ACKs via mobile APs is that the source node may not need to comewithin wireless communication range of a fixed AP before the source nodeis able to determine whether or not the file (and therefore thebundle(s) carrying the file) has been successfully received at the DTN.A disadvantage of disseminating E2E ACKs via the mobile APs is that suchan approach may introduce additional load into the network, as the E2EACKs are broadcast on the wireless network until the source node isreached, and the source node may be far from nodes that are transportingsuch E2E ACKs.

In accordance with various aspects of the present disclosure, the nodeperforming the method of FIG. 9 may be an intermediate node between thesource of a bundle and a DTN server acting as the destination node. Insuch a situation, the actions of block 904 may comprise the intermediatenode deciding whether the intermediate node should replicate the bundleor store the bundle until the intermediate node comes within wirelesscommunication range of a fixed AP. In accordance with various aspects ofthe present disclosure, data storage and dissemination rules used by theintermediate node may, for example, set a maximum number of hops ontowhich the bundle should be replicated, and if the bundle hasn't reachedthe DTN in the maximum number of hops, the last mobile AP to receive itmay store it until coming into range of a fixed AP. The term “hop” maybe used herein to refer to one part/segment/link of the communicationpath from a source to a destination. In a network in accordance with thepresent disclosure, data storage and dissemination rules at a networknode may set the maximum number of times a bundle may be replicated bythat network node, and if the bundle hasn't reached the destination node(e.g., a DTN server) at the point where the bundle has been replicatedthe maximum number of times, the last network node to receive the bundle(e.g., a mobile AP) may, for example, store the bundle until the networknode comes into wireless communication range of a particular type ofnode (e.g., a fixed AP). Replicating a bundle one or more times allowsthe bundle to arrive quickly at the destination node, since the bundlemay be present in storage of several nodes of the network (e.g.,multiple mobile APs) and the first node carrying the bundle (e.g., amobile AP) that comes into wireless communication range of theparticular node (e.g., the fixed AP) may then send the bundle to thedestination node (e.g., the DTN server). Replicating a bundle alsoincreases the probability of delivery of the bundle, since there aremultiple copies of the same bundle in nodes of the network. Even if acopy of the bundle is dropped by one node (e.g., a mobile AP, due tofull storage device), the bundle may still be delivered by another nodehaving a copy of the bundle.

At block 904, the method of FIG. 9 may comprise, for example, a firstnode that receives a bundle and may forward that bundle to a secondnetwork node (e.g., another device such as a MAP, FAP, NC, etc.), andthat the first node may then decide whether to drop the bundle from itsstorage. For example, an ACK for the bundle, received by the first nodefrom the second node, may comprise an indication that the second node isaccepting custody of the bundle. In such a situation, the first node maydetermine that it no longer has to store the bundle. One advantage ofthis approach is that such transfer of custody between nodes reducesoverall storage required in the network. A disadvantage of this approachis that transferring custody to the second node and deleting the bundleat the first node may increase the likelihood that a bundle fails toreach its destination. Whether the second node accepts custody of thebundle may, for example, be based on context information available tothe second node. Such context information may include information aboutthe first (sending) node and/or the second (receiving) node that permitsthe second node to determine whether or not the second node is morelikely to deliver the bundle to its final destination than the firstnode. For example, the context information available to the second nodemay be analyzed by the second node or a Cloud-based resource. Such adetermination may, for example, indicate that the second node is withinwireless communication range of a particular type of network node (e.g.,a fixed AP) more frequently and/or for longer period(s) of time than thefirst node, from which it received the bundle. Similarly, whether thefirst node drops the bundle in response to the ACK indicating acceptanceof custody by the second node may, for example, be based on contextinformation available to the first node that indicates which of thefirst node and the second node is more likely to deliver the bundle tothe final destination of the bundle.

In a network according to various aspects of the present disclosure, oneor more particular type(s) of network nodes (e.g., a fixed AP, a mobileAP in a stopped/parked vehicle (e.g., an autonomous electric vehiclethat is being charged)) may be used as anchor nodes for communication ofcontrol information between a first network node (e.g., a DTN server)and other network nodes (e.g., mobile APs). The anchor nodes (e.g.,fixed APs) may reliably communicate with the first network node (e.g.,the DTN server), and thus can be used to retrieve information about thestatus of the bundles/files that arrive at the first network node (e.g.,DTN server), or any other information that helps to manage the databeing stored and disseminated in a network as described herein. Anadvantage of using anchor nodes (e.g., fixed APs, MAPs of stopped/parkedvehicles, etc.) in this manner is that such an arrangement may improvethe efficiency of bundle storage and opportunistic communication ofdata, since the other network nodes (e.g., mobile APs) may then knowwhich bundles have already been delivered and which bundles are stillwaiting to be delivered. In accordance with various aspects of thepresent disclosure, network nodes such as, for example, fixed APs andMAPs of stopped/parked vehicles may be used as anchors for controlinformation between a DTN server (e.g., DTN server 720) and othernetwork nodes (e.g., mobile APs), when the density of the other networknodes is too low to reliably ensure dissemination of the information,and may not be used as anchors when density of the other network nodes(e.g., mobile APs) is high enough such that the other network nodes(e.g., mobile APs) are able to obtain all of the relevant informationfrom neighboring nodes (e.g., other mobile APs in proximity).

In accordance with various aspects of the present disclosure, certaintypes of network nodes (e.g., mobile APs) may choose to use a certaintype of communication link (e.g., a cellular connection, a Wi-Ficonnection, a DSRC connection) to access context information asdescribed above, from a remote resource (e.g., the Cloud). An advantageof this aspect of a network node of the present disclosure is that theremote resource (e.g., the Cloud) may be equipped with significant morecomputing and storage resources than nodes of the network, which mayenable the remote resource to quickly analyze data from the entirenetwork. Whether or not, and/or when any given node of the network(e.g., mobile AP) chooses to use the certain type of communication linkin this manner may depend on context information that may indicate, forexample, when a particular mobile AP is predicted to be in-range of afixed AP, how long a particular mobile AP typically spends in-range of afixed AP, etc.

In accordance with aspects of the present disclosure, a particular typeof network node (e.g., a mobile AP) may resort to the use of a specifictype of communication link (e.g., a cellular connection) for thedelivery of a bundle only as a last resort. This may happen when, forexample, the storage of a network node of the particular type (e.g.,mobile AP) is nearing maximum capacity, and the network node has noneighbor network nodes to which one or more bundles may be offloaded, orwhen the “time-to-live” of the bundle is expiring soon and the networknode is not predicted to be within wireless communication range ofanother node (e.g., a fixed AP) before the “time-to-live” of the bundlewill expire.

In accordance with various aspects of the present disclosure, contextinformation may include, for example, distributed and/or probabilisticmetrics calculated by one or more nodes of the network (e.g., MAPs,FAPs, NCs, etc.). This may involve, for example, each mobile AP locallysharing context information with neighbor nodes (e.g., FAPs, NCs, otherMAPs, etc.), and each mobile AP may then decide how to handle receivedbundles based on history and such probabilistic metrics. A network nodemay, for example, estimate one or more “contact times” and “contactdurations” when opportunities for wireless communication with anothernetwork node (e.g., one or more fixed APs) may occur; determinerespective amounts of storage available in one or more neighbor nodes;receive the identities and sizes of bundles stored in neighbor nodes,etc.; and may, in response, configure its own data storage anddissemination rules accordingly.

In accordance with various aspects of the present disclosure, nodes ofthe network (e.g., devices such as mobile APs, fixed APs, and/or a DTNserver) may maintain (e.g., either individually and/or collectively) oneor more “whitelists” and/or “blacklists” of specific network nodes towhich bundles should not be sent, for some particular period of time. Ablacklist maintained locally by a network node helps the node to managethe bundles, avoiding useless communications with neighbor nodes thatmay, for example, be dynamically evaluated and marked as not beingreliable. Certain nodes of the network may be placed on a blacklistwhen, for example, one or more network nodes determine that the storageof such network nodes is almost/totally full, that previouscommunications with such network nodes have failed, that such networknodes are having software and/or hardware problems, and/or the like.Such lists of network nodes help to avoid unnecessary network traffic,and make more efficient usage of opportunities to communicate betweennodes.

FIGS. 10A and 10B show a flowchart 1000 illustrating an example methodof routing and replication of data, in accordance with various aspectsof the present disclosure. FIGS. 10A-10B show additional detail of someof the actions of the flowchart 900 illustrated in FIG. 9. The method ofFIGS. 10A-10B may be performed by, for example, a node (e.g., a MAP) ofa network as illustrated and described in regards to FIGS. 1-8. Thefollowing discussion makes frequent reference to the use of “contextinformation.” Additional details about the nature of such “contextinformation” have been previously described above.

The method of FIGS. 10A-10B may be initiated at the startup of variousnodes of the network (e.g., as a process/thread started when anunderlying operating system begins running), and may run on a continuingbasis, once started. The actions of the method begin at block 1002,where the node performing the method (e.g., a mobile AP) determineswhether the node has received a bundle of data. A bundle of data may bereceived from, for example, another node (e.g., a FAP or MAP of FIGS.1-7) in the network. If, at block 1002, the node determines that abundle has been received, the node may then, at block 1004, determine(e.g., based on the contents of the bundle, and/or on contextinformation, described above) whether to acknowledge receipt of thebundle to the sender of the bundle. Next, at block 1006, the node maydetermine whether an acknowledgement (i.e., ACK) is to be sent, and thenode may then send the acknowledgement, at block 1008. As previouslydiscussed above, for example with regard to FIGS. 8 and 9, such anacknowledgement may, for example, include one or more flags, and mayindicate that the node is accepting custody of the bundle. The method ofFIG. 10A then continues to block 1014. If, however, at block 1006, it isdetermined that no acknowledgement is to be sent, control may pass toblock 1014.

Returning to block 1002, if it is determined that the node has notreceived a bundle from another network node, the method may thencontinue at block 1010, where a determination is made as to whether thenode itself has data to be sent in a bundle. For example, the node mayhave data from one or more sensors connected to the node, or the nodemay have a bundle that was stored and is to be sent to, for example,another node (e.g., a node that requested the bundle), or anotherdestination (e.g., the DTN or Cloud). If, at block 1010, it isdetermined that the node has data to be sent, then control is passed toblock 1012, and the node performing the method assembles a bundle, usingits own data and/or data from one or more stored bundles, based on, forexample, context information and data retention and dissemination rules.If, at block 1010, it is determined that there is no data to be sent bythe node, the method of FIG. 10A may simply return to block 1002.

When the method of FIG. 10A arrives at block 1014, the node performingthe method of FIG. 10A is in possession of a bundle (e.g., eitherreceived from another node, or assembled/built at the node). At block1014, the method determines whether the direction of the bundle is“upstream” (i.e., to the Cloud or DTN server), or “downstream” (i.e.,from the Cloud or DTN server to a destination node of the network). Ifit is determined that the bundle is directed “downstream,” the methodproceeds to block 1016, where the node records that handling of thebundle is to use a set of data retention and dissemination rules for usein processing bundles directed “downstream.” If, however, the nodeperforming the method, at block 1014, determined that the destination ofthe bundle is “upstream,” the method then proceeds to block 1018, wherethe node records that handling of the bundle is to use a set of dataretention and dissemination rules for use in processing bundles directed“upstream.”

Next, at block 1020, the method may make a determination of whether ornot to store the bundle at the node performing the method. Thedetermination may be based, for example, on the set of retention anddissemination rules for the direction of the bundle (i.e., “upstream” or“downstream”), and on context information such as that previouslydescribed above (that may be continually gathered by the node). Then, atblock 1022, if the determination of block 1020 was to store the bundle,control passes to block 1024, where the bundle may be stored in any ofthe types of memory available at the node, based on the contextinformation and the set of retention and dissemination rules currentlyin use. The method may also set a period of time during which the bundlemay be stored at the node. After that period of time, the bundle may bediscarded/dropped by the node, and may be sent to the destination by analternate, possibly more costly, communication path. The method may thencontinue at block 1026 shown in FIG. 10B. If, however, at block 1022,the determination of block 1020 was found to not store the bundle, thecontrol in the method of FIG. 10A simply passes to block 1026 of FIG.10B.

At block 1026 of FIG. 10B, a determination is made as to whether a“time-to-live” of the bundle has expired. A “time-to-live” parameter maybe part of the bundle and may, for example, indicate an amount of realtime, or a number of network hops until the “time-to-live” is consideredto have expired and alternative action (e.g., dropping the bundle) maybe taken. If, at block 1026, it is found that the “time-to-live” of thebundle has expired then, at block 1028, the bundle may be “dropped”(i.e., discarded) and storage for the bundle may be freed by the nodeperforming the method, and the method may then return to node 1002,described above. However, if it is found, at block 1026, that the“time-to-live” of the bundle has not yet expired then, at block 1030,the method may determine whether the bundle may be transmitted by thenode at this time. If it was determined, at block 1030, that the bundleis not to be transmitted, then control of the method may return to block1002, described above. If, however, it was determined that the bundle isto be transmitted at this time, the method of FIG. 10B may continue atblock 1032.

At block 1032, the method makes a determination as to whether toreplicate the bundle for transmission to two or more neighbor nodes.This determination may be made using, for example, the set of retentionand dissemination rules for the direction of bundle transport, and thetransmission may use, for example, unicast messages. Bundle replicationmay occur when transmit paths from the current node to neighboring nodessuffer interference, low signal strengths, or other impairments orrestrictions, as indicated by context information, and replication maypermit faster, more reliable and higher quality delivery of the bundlein such conditions. If the method determines, at block 1032, toreplicate the current bundle then, at block 1034, control may be passedto block 1038, where the bundle may be replicated for transmission toneighbor nodes over multiple communication paths, based on the contextinformation gathered by the node, and the method of FIG. 10B continuesat block 1036, described below. If, however, the method determines, atblock 1032, that replication of the bundle is not necessary then, atblock 1034 control is passed to block 1036, described below.

At block 1036, the bundle(s) may be scheduled for transmission via theavailable communication path(s), according to the context informationknow to the node, and the set of retention and dissemination rules ineffect for the direction of the bundle(s). Next, at block 1040, adetermination is made as to whether the node is to wait foracknowledgement from the neighbor(s) to which the bundle(s) weretransmitted. If, for example, the context information known to the nodeand the set of retention and dissemination rules for the bundledirection indicate that the node is to wait for acknowledgements then,at block 1042, the node may verify that an acknowledgement has beenreceived from each neighbor(s) to which the bundle was transmitted,before the method returns to block 1002, described above. If, however,the determination made at block 1030 as to whether the node is to waitfor acknowledgement from the neighbor(s) to which the bundle(s) weretransmitted indicates that no acknowledgements are required, the methodof FIG. 10B may return to block 1002, described above.

FIGS. 11A through 11C are a flowchart 1100 illustrating an examplemethod of operating a node, in accordance with various aspects of thepresent disclosure. FIGS. 11A-11C show additional detail of some of theactions of the flowchart illustrated in FIG. 9. The method of FIGS.11A-11C may be performed by, for example, a node (e.g., a MAP) of anetwork as illustrated and described in regards to FIGS. 1-8. Thefollowing discussion makes frequent reference to the use of “contextinformation,” additional details, the nature of, which have beenpreviously described above. The method of FIGS. 11A-11C may be initiatedat the startup of various nodes of the network (e.g., as aprocess/thread started when an underlying operating system beginsrunning), and may run on a continuing basis, once started. The actionsof the method begin at block 1102. It should be noted that the actionsshown in FIGS. 11A-11C may not be performed in the order shown, and thatactions of a block may, for example, be performed by a separateprocess/thread, while the process/thread of the method as a whilecontinues on with other actions.

At block 1102, the example method of FIG. 11A determines whether thenode running the method is a certain type of node (e.g., a mobile AP),and if the node is determined to be the certain type of node, the methodmay continue at block 1104, where the method may establish communicationvia a control channel (e.g., using DSRC) with one or more other networknodes (e.g., fixed APs, a DTN server and/or the Cloud). The node maythen, at block 1106, gather the network context information referred toabove, from the network nodes with which communication was able to beestablished, and then may continue on at block 1108. If, however, thenode performing the method of FIGS. 11A-11C is determined, at block1102, to be a type of network node other than certain type of node then,at block 1102, the node performing the method may continue at block1108.

Next, at block 1108, the method of FIG. 11A may determine whether thenode has any bundles stored in the various types of memory that may bepresent on the node. If one or more bundle(s) is/are stored on the node,the method may continue at block 1110, where the node may begin toperiodically advertise information about the bundles currently stored onthe node. Advertisement may permit the neighbor nodes to determinewhether any bundles that those neighbor nodes need are available fromthe node sending the advertisement. Such advertisements may betransmitted as one or a series of repeating transmissions of bundlesavailable from the node using, for example, unicast, multicast, orbroadcast-type messages sent into the network by, for example, aprocess/thread of the node. Once transmission of such advertisements hasbeen initiated, the method of FIG. 11A may then continue at block 1112.If, however, at block 1108, the method of FIG. 11A determines that thecurrent node has no stored bundles to advertise, the method of FIG. 11Amay end transmission of any advertisements of needed/wanted bundles(e.g., terminating any corresponding process/thread), and may continueat block 1112 of FIG. 11A.

At block 1112, the method of FIG. 11A may determine whether the nodeneeds/wants any bundles that may be stored in the various types ofmemory that may be present on a neighbor node. If one or more bundle(s)are needed/wanted by the node, the method may continue at block 1114,where the node may begin to periodically advertise information about thebundles that are needed/wanted by the node. This may permit the neighbornodes to determine whether any bundles that those neighbor nodes havestored in memory are needed/wanted by the node that sent theadvertisement. Such advertisements may be transmitted as one or a seriesof repeating transmissions of bundles needed/wanted by the node using,for example, unicast, multicast, or broadcast-type messages sent intothe network by a process/thread. Once transmission of suchadvertisements has been initiated, the method may then continue at block1116 of FIG. 11B. If, however, at block 1112, the method determines thatthe current node does not need/want any bundles, the method of FIG. 11Amay then end any such advertisements, if active, and continue at block1116 of FIG. 11B.

At block 1116, the node performing the method of FIGS. 11A-11C maydetermine whether it has received any advertisements of bundles storedat one or more neighbor node(s). If no such advertisements have beenreceived by this node, the method may pass control to block 1132,described below. If, however, at block 1116, the node determines thatone or more advertisements of stored bundles have been received by thisnode then, at block 1118, the node may determine whether any of thebundles advertised by a neighbor node are needed/wanted by this nodeusing, by way of example and not limitation, information in theadvertisements, and/or one or more items from the gathered contextinformation previously discussed, above. Next, at block 1120, if it wasdetermined that one or more bundles needed/wanted by this node have beenadvertised as available at one or more neighbor node(s), the nodeperforming the method may then, at block 1122, request and receive theneeded/wanted bundles from the advertising neighbor node(s) (e.g., viadownload). The method of FIG. 11B then continues at block 1124.

At block 1124, the node performing the method of FIG. 11B may thendetermine whether one or more of the bundles in advertisements receivedby this node may be forwarded to other nodes. For example, in accordancewith aspects of the present disclosure, a node may receive anadvertisement of bundles needed/wanted by a first neighbor node, and mayreceive an advertisement of bundles available from a second neighbornode, and may then determine that certain bundles needed/wanted by thefirst neighbor node are available from the second neighbor node. Suchforwarding may, for example, be governed by the context information atthe node, the set of retention and dissemination rules in effect for thenode(s) (e.g., based upon bundle direction), and parameters of thebundle(s). At block 1126, if there are no bundles to be forwardedbetween neighbor nodes, the method of FIG. 11B may then continue atblock 1132 of FIG. 11C. If, however, it is determined, at block 1126,that there are bundles that may be forwarded by this node from oneneighbor node to another neighbor node, the node performing the methodof FIG. 11B may, at block 1128 and block 1128, perform the downloadingand forwarding of the bundles. The method of FIG. 11B then proceeds toblock 1132 of FIG. 11C.

At block 1132 of FIG. 11C, the method of FIGS. 11A-11C may determinewhether the node performing the method has received, from one or moreneighbor nodes, advertisements that identify one or more bundlesneeded/wanted by the neighbor node(s). If the node has not received anysuch advertisements, the node performing the method may then return toblock 1102, described above. If, however, the node has received one ormore advertisements of regarding bundles needed/wanted by one or moreneighbor node(s), then, at block 1134, the node performing the methodmay then determine whether the bundles needed/wanted by the neighbornode(s) is/are stored at the node performing the method. Next, at block1136, it is determined that the node does not have the bundle(s)needed/wanted by the neighbor node then the method of FIG. 11C returnsto block 1102. If, however, it was determined, at block 1136, that thenode performing the method does have one or more of the bundles(s)needed/wanted by the neighbor node(s) then, at block 1138, a check maybe made to determine whether it is permissible for the node performingthe method to provide the needed/wanted bundles to the neighbor nodesthat advertised to find those bundles. If, at block 1138, it isdetermined that it is permissible for the node performing the method toprovide the needed/wanted bundles to the neighbor node(s), then thenode, at block 1140, provides the bundle(s) needed/wanted by theneighbor node(s) and stored at the node performing the method, to theneighbor node(s) that advertise the need/want for the respectivebundle(s). The method of FIG. 11C then returns to block 1102, describedabove.

Various aspects of the present disclosure may be found in a method ofmanaging routing and replication of data at a first node of a networkcomprising a plurality of nodes. Such a method may comprise wirelesslyestablishing communication with one or more other nodes of the pluralityof nodes; and gathering operating parameters of the first node and ofthe one or more other nodes via one or more wireless communicationlinks, the gathering producing a collection of context information atthe first node. The method may also comprise determining whether a databundle is available for processing by the first node. The method mayfurther comprise, if a data bundle is available for processing by thefirst node, choosing to perform one of the following actions with thedata bundle, based on the context information and a set of rules for thefirst node for a direction of communication of the data bundle:transmitting the data bundle from the first node towards a second nodeof the plurality of nodes via a number of communication links, storingthe data bundle at the first node, and dropping the data bundle frommemory of the first node.

In accordance with various aspects of the present disclosure, the firstnode may be located in a vehicle movable about a service area of thenetwork, and the first node may be a mobile access point configured towirelessly communicate with end-user devices accessing the network. Theplurality of nodes may comprise one or more nodes that are located at afixed geographic location and one or more nodes that are mobile.Determining whether a data bundle is available may comprise one or moreof determining that a data bundle is available and assembling the databundle using data originating at the first node, if data originating atthe first node is available for transmission by the first node;determining that a data bundle is available and providing the databundle from storage of the first node, if one or more data bundles areavailable in storage at the first node for transmission by the firstnode; and determining that a data bundle is not available, otherwise.Assembling the data bundle using data originating at the first node maycomprise forming the data bundle using signals from one or more sensorsoperatively coupled to the first node. The set of rules for the firstnode for a direction of communication of the data bundle may be selectedfrom two or more sets of rules comprising a set of rules for firstdirection through the network and a set of rules for a downstream asecond direction through the network. In accordance with aspects of thedisclosure, the first direction may be towards a Cloud-based system andthe second direction may be away from the Cloud-based system.Transmitting the data bundle from the first node towards a second nodeof the plurality of nodes via the number of communication links maycomprise determining that the number of communication links is two ormore, based on the context information indicative of quality ofcommunication of the first node with neighbor nodes of the plurality ofnodes. Transmitting the data bundle from the first node may comprisereplicating the data bundle to result in the number of copies of thedata bundle for transmission by the first node via respectivecommunication links.

Various aspects of the present disclosure may be observed in anon-transitory computer-readable medium having a plurality of codesections, where each code section stores a plurality of instructionsexecutable by one or more processors. The executable instructions maycause the one or more processors to perform a method of managing routingand replication of data at a first node of a network comprising aplurality of nodes, where the steps of the method are as describedabove.

Further aspects of the present disclosure may be seen in a system formanaging routing and replication of data at a first node of a networkcomprising a plurality of nodes. Such a system may comprise one or moreprocessors operatively coupled to at least one wireless interface forcommunicatively coupling the first node to other nodes of the network.In such a system, the one or more processors may be operable to, atleast, perform the steps of a method of managing routing and replicationof data at a first node of a network, such as the method describedabove.

In accordance with various aspects of this disclosure, examples of thenetworks and/or components thereof presented herein are provided in U.S.Provisional Application Ser. No. 62/222,192, titled “CommunicationNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

In accordance with various aspects of this disclosure, the networksand/or components thereof presented herein are provided with systems andmethods for integrating such networks and/or components with othernetworks and systems, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/221,997, titled “IntegratedCommunication Network for A Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for synchronizing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,016, titled “Systems and Methods forSynchronizing a Network of Moving Things,” filed on Sep. 22, 2015, whichis hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,042, titled “Systems and Methods forManaging a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for monitoring such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,066, titled “Systems and Methods forMonitoring a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for detecting and/or classifying anomalies insuch networks and/or components, non-limiting examples of which areprovided in U.S. Provisional Application Ser. No. 62/222,077, titled“Systems and Methods for Detecting and Classifying Anomalies in aNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,098, titled “Systems and Methodsfor Managing Mobility in a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing connectivity in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,121, titled “Systems and Methodsfor Managing Connectivity a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for collecting sensor data in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,135, titled “Systems and Methodsfor Collecting Sensor Data in a Network of Moving Things,” filed on Sep.22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for interfacing with such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,145, titled “Systems and Methodsfor Interfacing with a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for interfacing with a user of such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,150, titled “Systems and Methodsfor Interfacing with a User of a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for data storage and processing in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,168, titled “Systems and Methodsfor Data Storage and Processing for a Network of Moving Things,” filedon Sep. 22, 2015, which is hereby incorporated herein by reference inits entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for vehicle traffic management in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,183, titled “Systems and Methodsfor Vehicle Traffic Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for environmental management in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,186, titled “Systems and Methodsfor Environmental Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing port or shipping operation in suchnetworks and/or components, non-limiting examples of which are providedin U.S. Provisional Application Ser. No. 62/222,190, titled “Systems andMethods for Port Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of positioning orlocation information based at least in part on historical data,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/244,828, titled “Utilizing Historical Data toCorrect GPS Data in a Network of Moving Things,” filed on Oct. 22, 2015,which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of position or locationof positioning or location information based at least in part on theutilization of anchors, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/244,930, titled “Using Anchorsto Correct GPS Data in a Network of Moving Things,” filed on Oct. 22,2015, which is hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing communication between applications,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/246,368, titled “Systems and Methods forInter-Application Communication in a Network of Moving Things,” filed onOct. 26, 2015, which is hereby incorporated herein by reference in itsentirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for probing, analyzing and/or validatingcommunication, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/246,372, titled “Systems and Methodsfor Probing and Validating Communication in a Network of Moving Things,”filed on Oct. 26, 2015, which is hereby incorporated herein by referencein its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for adapting communication rate, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/250,544, titled “Adaptive Rate Control for Vehicular Networks,” filedon Nov. 4, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for reconfiguring and adapting hardware,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/273,878, titled “Systems and Methods forReconfiguring and Adapting Hardware in a Network of Moving Things,”filed on Dec. 31, 2015, which is hereby incorporated herein by referencein its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for optimizing the gathering of data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/253,249, titled “Systems and Methods for Optimizing Data Gathering ina Network of Moving Things,” filed on Nov. 10, 2015, which is herebyincorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing delay tolerant networking,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/257,421, titled “Systems and Methods for DelayTolerant Networking in a Network of Moving Things,” filed on Nov. 19,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for improving the coverage and throughput ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/265,267, titled “Systems andMethods for Improving Coverage and Throughput of Mobile Access Points ina Network of Moving Things,” filed on Dec. 9, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for coordinating channel utilization, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,858, titled “Channel Coordination in a Network of Moving Things,”filed on Dec. 22, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for implementing a network coded mesh network in thenetwork of moving things, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/257,854, titled “Systems andMethods for Network Coded Mesh Networking in a Network of MovingThings,” filed on Nov. 20, 2015, which is hereby incorporated herein byreference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for improving the coverage of fixed access points,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/260,749, titled “Systems and Methods forImproving Fixed Access Point Coverage in a Network of Moving Things,”filed on Nov. 30, 2015, which is hereby incorporated herein by referencein its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility controllers and their networkinteractions, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/273,715, titled “Systems and Methodsfor Managing Mobility Controllers and Their Network Interactions in aNetwork of Moving Things,” filed on Dec. 31, 2015, which is herebyincorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for managing and/or triggering handovers ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/281,432, titled “Systems andMethods for Managing and Triggering Handovers of Mobile Access Points ina Network of Moving Things,” filed on Jan. 21, 2016, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing captive portal-related control andmanagement, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/268,188, titled “CaptivePortal-related Control and Management in a Network of Moving Things,”filed on Dec. 16, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for extrapolating high-value data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,678, titled “Systems and Methods to Extrapolate High-Value Datafrom a Network of Moving Things,” filed on Dec. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote software updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/272,750, titled “Systems and Methodsfor Remote Software Update and Distribution in a Network of MovingThings,” filed on Dec. 30, 2015, which is hereby incorporated herein byreference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote configuration updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/278,662, titled “Systems and Methodsfor Remote Configuration Update and Distribution in a Network of MovingThings,” filed on Jan. 14, 2016, which is hereby incorporated herein byreference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for adapting the network, for exampleautomatically, based on user feedback, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,243, titled“Systems and Methods for Adapting a Network of Moving Things Based onUser Feedback,” filed on Jan. 22, 2016, which is hereby incorporatedherein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing and/or guaranteeing data integritywhen building or performing data analytics, non-limiting examples ofwhich are provided in U.S. Provisional Application Ser. No. 62/278,764,titled “Systems and Methods to Guarantee Data Integrity When BuildingData Analytics in a Network of Moving Things,” Jan. 14, 2016, which ishereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing self-initialization and/or automatedbootstrapping of mobile access points, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,515, titled“Systems and Methods for Self-Initialization and Automated Bootstrappingof Mobile Access Points in a Network of Moving Things,” filed on Jan.25, 2016, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing power supply and/or utilization,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/295,602, titled “Systems and Methods for PowerManagement in a Network of Moving Things,” filed on Feb. 16, 2016, whichis hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for automating and easing the installation and setupof the infrastructure, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/299,269, titled “Systems andMethods for Automating and Easing the Installation and Setup of theInfrastructure Supporting a Network of Moving Things,” filed on Feb. 24,2016, which is hereby incorporated herein by reference in its entirety.

In summary, various aspects of this disclosure provide communicationnetwork architectures, systems and methods for supporting a network ofmobile nodes, for example comprising a combination of mobile andstationary nodes. As a non-limiting example, various aspects of thisdisclosure provide communication network architectures, systems, andmethods for supporting a dynamically configurable communication networkcomprising a complex array of both static and moving communication nodes(e.g., the Internet of moving things). While the foregoing has beendescribed with reference to certain aspects and examples, it will beunderstood by those skilled in the art that various changes may be madeand equivalents may be substituted without departing from the scope ofthe disclosure. In addition, many modifications may be made to adapt aparticular situation or material to the teachings of the disclosurewithout departing from its scope. Therefore, it is intended that thedisclosure not be limited to the particular example(s) disclosed, butthat the disclosure will include all examples falling within the scopeof the appended claims.

The present method and/or system may be realized in hardware, software,or a combination of hardware and software. The present methods and/orsystems may be realized in a centralized fashion in at least onecomputing system, or in a distributed fashion where different elementsare spread across several interconnected computing systems. Any kind ofcomputing system or other apparatus adapted for carrying out the methodsdescribed herein is suited. A typical combination of hardware andsoftware may be a general-purpose computing system with a program orother code that, when being loaded and executed, controls the computingsystem such that it carries out the methods described herein. Anothertypical implementation may comprise an application specific integratedcircuit or chip. Some implementations may comprise a non-transitorymachine-readable (e.g., computer readable) medium (e.g., FLASH drive,optical disk, magnetic storage disk, or the like) having stored thereonone or more lines of code executable by a machine, thereby causing themachine to perform processes as described herein.

While the present method and/or system has been described with referenceto certain implementations, it will be understood by those skilled inthe art that various changes may be made and equivalents may besubstituted without departing from the scope of the present methodand/or system. In addition, many modifications may be made to adapt aparticular situation or material to the teachings of the presentdisclosure without departing from its scope. Therefore, it is intendedthat the present method and/or system not be limited to the particularimplementations disclosed, but that the present method and/or systemwill include all implementations falling within the scope of theappended claims.

1. A method of managing routing and replication of data at a first nodeof a network comprising a plurality of nodes, the method comprising:wirelessly establishing communication with one or more other nodes ofthe plurality of nodes; gathering operating parameters of the first nodeand of the one or more other nodes via one or more wirelesscommunication links, the gathering producing a collection of contextinformation at the first node; determining whether a data bundle isavailable for processing by the first node; and if a data bundle isavailable for processing by the first node, choosing to perform one ofthe following actions with the data bundle, based on the contextinformation and a set of rules for the first node for a direction ofcommunication of the data bundle: transmitting the data bundle from thefirst node towards a second node of the plurality of nodes via a numberof communication links, storing the data bundle at the first node, anddropping the data bundle from memory of the first node.
 2. The methodaccording to claim 1, wherein the first node is located in a vehiclemovable about a service area of the network.
 3. The method according toclaim 1, wherein the first node is a mobile access point configured towirelessly communicate with end-user devices accessing the network. 4.The method according to claim 1, wherein the plurality of nodescomprises one or more nodes that are located at a fixed geographiclocation and one or more nodes that are mobile.
 5. The method accordingto claim 1, wherein determining whether a data bundle is availablecomprises one or more of: determining that a data bundle is availableand assembling the data bundle using data originating at the first node,if data originating at the first node is available for transmission bythe first node; determining that a data bundle is available andproviding the data bundle from storage of the first node, if one or moredata bundles are available in storage at the first node for transmissionby the first node; and determining that a data bundle is not available,otherwise.
 6. The method according to claim 5, wherein assembling thedata bundle using data originating at the first node comprises: formingthe data bundle using signals from one or more sensors operativelycoupled to the first node.
 7. The method according to claim 1, whereinthe set of rules for the first node for a direction of communication ofthe data bundle is selected from two or more sets of rules comprising aset of rules for a first direction through the network and a set ofrules for a second direction through the network.
 8. The methodaccording to claim 7, wherein the first direction is towards aCloud-based system and the second direction is away from the Cloud-basedsystem.
 9. The method according to claim 1, wherein transmitting thedata bundle from the first node towards a second node of the pluralityof nodes via the number of communication links comprises determiningthat the number of communication links is two or more, based on thecontext information indicative of quality of communication of the firstnode with neighbor nodes of the plurality of nodes.
 10. The methodaccording to claim 9, wherein transmitting the data bundle from thefirst node comprises replicating the data bundle to result in the numberof copies of the data bundle for transmission by the first node viarespective communication links.
 11. A non-transitory computer-readablemedium having a plurality of code sections, each code section storing aplurality of instructions executable by one or more processors to causethe one or more processors to perform a method of managing routing andreplication of data at a first node of a network comprising a pluralityof nodes, the steps of the method comprising: wirelessly establishingcommunication with one or more other nodes of the plurality of nodes;gathering operating parameters of the first node and of the one or moreother nodes via one or more wireless communication links, the gatheringproducing a collection of context information at the first node;determining whether a data bundle is available for processing by thefirst node; and if a data bundle is available for processing by thefirst node, choosing to perform one of the following actions with thedata bundle, based on the context information and a set of rules for thefirst node for a direction of communication of the data bundle:transmitting the data bundle from the first node towards a second nodeof the plurality of nodes via a number of communication links, storingthe data bundle at the first node, and dropping the data bundle frommemory of the first node.
 12. The non-transitory computer-readablemedium according to claim 11, wherein the first node is located in avehicle movable about a service area of the network.
 13. Thenon-transitory computer-readable medium according to claim 11, whereinthe first node is a mobile access point configured to wirelesslycommunicate with end-user devices accessing the network.
 14. Thenon-transitory computer-readable medium according to claim 11, whereinthe plurality of nodes comprises one or more nodes that are located at afixed geographic location and one or more nodes that are mobile.
 15. Thenon-transitory computer-readable medium according to claim 11, whereindetermining whether a data bundle is available comprises one or more of:determining that a data bundle is available and assembling the databundle using data originating at the first node, if data originating atthe first node is available for transmission by the first node;determining that a data bundle is available and providing the databundle from storage of the first node, if one or more data bundles areavailable in storage at the first node for transmission by the firstnode; and determining that a data bundle is not available, otherwise.16. The non-transitory computer-readable medium according to claim 15,wherein assembling the data bundle using data originating at the firstnode comprises: forming the data bundle using signals from one or moresensors operatively coupled to the first node.
 17. The non-transitorycomputer-readable medium according to claim 11, wherein the set of rulesfor the first node for a direction of communication of the data bundleis selected from two or more sets of rules comprising a set of rules fora first direction through the network and a set of rules for a seconddirection through the network.
 18. The non-transitory computer-readablemedium according to claim 17, wherein the first direction is towards aCloud-based system and the second direction is away from the Cloud-basedsystem.
 19. The non-transitory computer-readable medium according toclaim 11, wherein transmitting the data bundle from the first nodetowards a second node of the plurality of nodes via the number ofcommunication links comprises determining that the number ofcommunication links is two or more, based on the context informationindicative of quality of communication of the first node with neighbornodes of the plurality of nodes.
 20. The non-transitorycomputer-readable medium according to claim 19, wherein transmitting thedata bundle from the first node comprises replicating the data bundle toresult in the number of copies of the data bundle for transmission bythe first node via respective communication links.
 21. A system formanaging routing and replication of data at a first node of a networkcomprising a plurality of nodes, the system comprising: one or moreprocessors operatively coupled to at least one wireless interface forcommunicatively coupling the first node to other nodes of the network,the one or more processors operable to, at least: wirelessly establishcommunication with one or more other nodes of the plurality of nodes;gather operating parameters of the first node and of the one or moreother nodes via one or more wireless communication links, the gatheringproducing a collection of context information at the first node;determine whether a data bundle is available for processing by the firstnode; and if a data bundle is available for processing by the firstnode, choosing to perform one of the following actions with the databundle, based on the context information and a set of rules for thefirst node for a direction of communication of the data bundle: transmitthe data bundle from the first node towards a second node of theplurality of nodes via a number of communication links, store the databundle at the first node, and drop the data bundle from memory of thefirst node.
 22. The system according to claim 21, wherein the first nodeis located in a vehicle movable about a service area of the network. 23.The system according to claim 21, wherein the first node is a mobileaccess point configured to wirelessly communicate with end-user devicesaccessing the network.
 24. The system according to claim 21, wherein theplurality of nodes comprises one or more nodes that are located at afixed geographic location and one or more nodes that are mobile.
 25. Thesystem according to claim 21, wherein determining whether a data bundleis available comprises one or more of: determining that a data bundle isavailable and assembling the data bundle using data originating at thefirst node, if data originating at the first node is available fortransmission by the first node; determining that a data bundle isavailable and providing the data bundle from storage of the first node,if one or more data bundles are available in storage at the first nodefor transmission by the first node; and determining that a data bundleis not available, otherwise.
 26. The system according to claim 25,wherein assembling the data bundle using data originating at the firstnode comprises: forming the data bundle using signals from one or moresensors operatively coupled to the first node.
 27. The system accordingto claim 21, wherein the set of rules for the first node for a directionof communication of the data bundle is selected from two or more sets ofrules comprising a set of rules for a first direction through thenetwork and a set of rules for a second direction through the network.28. The system according to claim 27, wherein the first direction istowards a Cloud-based system and the second direction is away from theCloud-based system.
 29. The system according to claim 21, whereintransmitting the data bundle from the first node towards a second nodeof the plurality of nodes via the number of communication linkscomprises determining that the number of communication links is two ormore, based on the context information indicative of quality ofcommunication of the first node with neighbor nodes of the plurality ofnodes.
 30. The system according to claim 29, wherein transmitting thedata bundle from the first node comprises replicating the data bundle toresult in the number of copies of the data bundle for transmission bythe first node via respective communication links.